Audit Report (Token)
Paladin reviewed Freemoon (Audit Report (Token)) on 14 Feb 2022: 11 findings, 0 critical; 8 marked fixed, 3 acknowledged.
No open critical findings
Open the reportOpen Freemoon’s security record
Report hosted on paladinsec.co.
Trustblock does not review code.
Findings11
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 4 |
| Medium | 0 | 2 | 1 |
| Low | 0 | 1 | 3 |
HighLack of boundary limit checks for setting of sensitive state variablesFixed
The report gives no description here.
HighLP tokens from addLiquidity are sent to ownerFixed
The report gives no description here.
HighOwnership of contract can be regained after renounced or transferredFixed
The report gives no description here.
HighsetRouterAddress could be used to siphon all liquidity fees or turn the token into a honeypotFixed
The report gives no description here.
MediumSensitive state variable modifying functions can be changed instantaneouslyFixed
The report gives no description here.
LowContract deployer is excluded from fees and maxTx in the constructorFixed
The report gives no description here.
LowLack of events for functions that change sensitive variablesFixed
The report gives no description here.
LowThe LP pair contract will receive reflection rewards which may be skimmedFixed
The report gives no description here.
Contracts in scope1
| Address | Chain | Source code |
|---|---|---|
| 0x0725384edd4637f7c26de9cd3c086c14071688d5 | Chain: BNB Chain | Source code: Verified source |
Part of Freemoon’s security record
FreemoonAudits2 audits by 1 firmLast audit Mar 2022, by Paladin.
Critical findingsNo open critical findingsAcross 2 reports.
Open Freemoon’s security recordSecurity firm
Paladin176 projects reviewed · 241 reports · latest Apr 2025
See Paladin’s auditsSomething 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