Pecunity

CFG Ninja1 address on BNB Chain

CFG Ninja reviewed Pecunity on 18 Nov 2025: 3 findings, 1 critical; none marked fixed.

1 open critical finding
Open the reportOpen Pecunity’s security record

Report hosted on GitHub.

Statuses are the security firm’s own, from this report. Trustblock does not review code.

Findings3

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical100
High100
Medium100
Low000
CriticalCentralization Risk in Launch MechanismNot fixed

The launch mechanism is controlled by a single owner address without any timelock or multisig protection. The owner has unilateral power to enable/disable transfers and control the launch state.

HighMissing Access Control RecoveryNot fixed

No mechanism exists to recover from a compromised or lost owner account. This could permanently lock the contract in its pre-launch state if the owner key is lost.

MediumPotential Sandwich AttacksNot fixed

A sandwich attack might happen when an attacker observes a transaction swapping tokens or adding liquidity without setting restrictions on slippage or minimum output amount.

Contracts in scope1

AddressChainSource code
Chain: BNB ChainSource code: Verified source

Part of Pecunity’s security record

Pecunity
Audits2 audits by 2 firmsLast audit Nov 2025, by CFG Ninja.
Critical findings1 open critical findingReported in “Pecunity” by CFG Ninja, Nov 2025. Not marked fixed in that report.
Open Pecunity’s security record

Security firm

CFG Ninja

566 projects reviewed · 697 reports · latest Jan 2026

See CFG Ninja’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us