The token contract implements an ERC-20 standard with custom taxation, anti-bot, and anti-whale mechanisms. While it uses SafeMath for arithmetic safety, it exhibits critical centralization risks. The owner possesses extensive control over vital parameters, including the ability to halt trading or manipulate token economics, posing a severe risk to user funds and the token's utility. The anti-bot features, while intended for protection, are also centrally controlled and can be misused.

On-chain security analysis — is it a scam or legit?
Is MOO DENG Safe?
Not verified
This record has not gone through deep verification and is not being monitored. The score is a dated snapshot — the token’s risk can change at any time.Own this token? Put it under verification →The token contract implements an ERC-20 standard with custom taxation, anti-bot, and anti-whale mechanisms.
- Top-10 concentration > 20%
- 1 Critical finding(s) from audit
- 1 High finding(s) from audit
- 1 Medium finding(s) from audit
- 1 Low finding(s) from audit
Exact factors
- Top-10 concentration > 20% (41.7% total → 28.5% effective; 19.7% in EOAs, 22.0% in contracts — mild)
- 1 Critical finding(s) from audit
- 1 High finding(s) from audit
- 1 Medium finding(s) from audit
- 1 Low finding(s) from audit
Each factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed
Security Checklist
as of audit · Sep 4Holders
as of audit · Sep 4, 2026- Contractstreasury, vesting, bridge, staking22.0%
- Walletsanonymous holders, free to sell19.7%
- Everyone elsethe rest of the supply58.3%
How holder types affect the score
Share held by contracts — treasury, vesting, bridge or staking — is discounted against share held by wallets when the score is computed: a contract cannot decide to sell the way an anonymous holder can, though it can still be drained or voted to sell. Effective concentration is the figure the risk score is actually calculated from.
Holder balances as recorded by the audit of Sep 4, 2026
Liquidity
as of audit · Sep 4The risk score reads depth across every pair.
The LP tokens of the analysed pool are locked or burned.
0x3f3b…05140x826f…1e650xb3ac…68a00x0000…8a900xaeff…db9a0x1f2f…f387No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
Security Findings
CriticalOwner Privileges and Centralization Risk
The contract owner possesses extensive control over critical token parameters, including the ability to set taxes (setInitialBuyTax, setFinalSellTax), transaction limits (setMaxTxAmount, setMaxWalletSize), manage bot lists (addBot, delBot), and enable/disable trading and swapping (openTrading, setSwapEnabled). This high degree of centralization allows the owner to manipulate the token's economy, halt trading by setting _maxTxAmount or _maxWalletSize to zero, or even redirect collected taxes by changing _taxWallet. A compromised owner key or a malicious owner could lead to a complete loss of user funds or render the token untradable.C-01
Issue
The contract owner possesses extensive control over critical token parameters, including the ability to set taxes (setInitialBuyTax, setFinalSellTax), transaction limits (setMaxTxAmount, setMaxWalletSize), manage bot lists (addBot, delBot), and enable/disable trading and swapping (openTrading, setSwapEnabled). This high degree of centralization allows the owner to manipulate the token's economy, halt trading by setting _maxTxAmount or _maxWalletSize to zero, or even redirect collected taxes by changing _taxWallet. A compromised owner key or a malicious owner could lead to a complete loss of user funds or render the token untradable.
Fix
Implement a multi-signature wallet for ownership or transition to a decentralized governance model. For highly sensitive functions, consider adding a time-lock mechanism to allow users to react to pending changes. Clearly communicate the extent of owner privileges to the community.
Status
Unresolved
HighAnti-Bot/Anti-Whale Mechanisms with Centralized Control
The contract includes anti-bot (bots mapping) and anti-whale (_maxTxAmount, _maxWalletSize, sellCount per block) mechanisms. While intended to protect against manipulation, these features are centrally controlled by the owner. The owner can arbitrarily add or remove addresses from the bots list, potentially blocking legitimate users. The sellCount limit per block can restrict users' ability to sell their desired amount, and can be circumvented by using multiple addresses. These mechanisms introduce subjective control and potential for abuse, impacting fair market operations and user liquidity.H-01
Issue
The contract includes anti-bot (bots mapping) and anti-whale (_maxTxAmount, _maxWalletSize, sellCount per block) mechanisms. While intended to protect against manipulation, these features are centrally controlled by the owner. The owner can arbitrarily add or remove addresses from the bots list, potentially blocking legitimate users. The sellCount limit per block can restrict users' ability to sell their desired amount, and can be circumvented by using multiple addresses. These mechanisms introduce subjective control and potential for abuse, impacting fair market operations and user liquidity.
Fix
Re-evaluate the necessity and implementation of these mechanisms. If retained, consider decentralizing control over the bots list through a community vote or a transparent, auditable process. Ensure that _maxTxAmount and _maxWalletSize are set to reasonable values that do not unduly restrict legitimate trading. Clearly document the behavior and limitations of these features.
Status
Unresolved
MediumHigh Initial Transaction Taxes
The contract is configured with high initial buy and sell taxes of 21% (_initialBuyTax, _initialSellTax). While these taxes are designed to reduce after certain _buyCount thresholds (_reduceBuyTaxAt, _reduceSellTaxAt), such high initial rates can deter early adoption, reduce trading volume, and create a perception of a 'honeypot' or an unsustainable economic model. This could negatively impact the token's liquidity and overall market health.M-01
Issue
The contract is configured with high initial buy and sell taxes of 21% (_initialBuyTax, _initialSellTax). While these taxes are designed to reduce after certain _buyCount thresholds (_reduceBuyTaxAt, _reduceSellTaxAt), such high initial rates can deter early adoption, reduce trading volume, and create a perception of a 'honeypot' or an unsustainable economic model. This could negatively impact the token's liquidity and overall market health.
Fix
Consider lowering the initial tax rates to more standard levels (e.g., 5-10%) to encourage early trading and adoption. Clearly communicate the tax structure, including initial rates and reduction thresholds, to potential investors. Monitor the impact of tax rates on trading volume and adjust as necessary through a controlled governance process.
Status
Unresolved
LowFront-running of openTrading Function
The openTrading() function, which enables transfers by setting tradingOpen = true, can be front-run. Malicious actors or bots can monitor the transaction pool for the openTrading() call and submit their own buy transactions with a higher gas price to be among the first to trade the token. This allows them to gain an unfair advantage in early trading, potentially buying at a lower price before wider market participation.L-01
openTrading FunctionIssue
The openTrading() function, which enables transfers by setting tradingOpen = true, can be front-run. Malicious actors or bots can monitor the transaction pool for the openTrading() call and submit their own buy transactions with a higher gas price to be among the first to trade the token. This allows them to gain an unfair advantage in early trading, potentially buying at a lower price before wider market participation.
Fix
While this is a common characteristic of new token launches and not a direct vulnerability in the contract's logic, projects should be aware of this risk. Consider alternative launch mechanisms or clearly communicate the launch strategy to manage community expectations. No direct code change is typically required for this inherent market dynamic.
Status
Unresolved
InfoImplications of Renouncing Ownership
The contract includes a renounceOwnership() function, which allows the current owner to transfer ownership to the zero address. If ownership is renounced, all functions protected by the onlyOwner modifier become permanently inaccessible. This means that critical parameters such as tax rates, transaction limits, wallet limits, and the bot list can never be changed, and any potential issues or desired updates cannot be addressed. While this increases decentralization, it also removes any ability to adapt or mitigate future problems.I-01
Issue
The contract includes a renounceOwnership() function, which allows the current owner to transfer ownership to the zero address. If ownership is renounced, all functions protected by the onlyOwner modifier become permanently inaccessible. This means that critical parameters such as tax rates, transaction limits, wallet limits, and the bot list can never be changed, and any potential issues or desired updates cannot be addressed. While this increases decentralization, it also removes any ability to adapt or mitigate future problems.
Fix
If the intention is to renounce ownership, ensure that all critical parameters are set to their final, desired state before renunciation. Clearly communicate the implications of renouncing ownership to the community, emphasizing that the contract will become immutable and unmanageable by any single entity.
Status
Unresolved
Analysis
AI Copilotas of audit · Sep 4The contract utilizes SafeMath to prevent integer overflows/underflows, which is a strong security practice (7.2 Code Security). However, the architecture grants the owner highly centralized control over critical functions and parameters, such as setMaxTxAmount and setInitialBuyTax (7.1 Architecture, 7.3 Access Control). This extensive control introduces a high technical risk, as a compromised owner key could lead to severe operational issues or fund manipulation.
The economic model incorporates initial buy and sell taxes (21%) which can be reduced based on _buyCount thresholds (7.4 Economic). While this provides flexibility, the initial high taxes could deter legitimate trading. The governance model is highly centralized, with the owner having unilateral control over all key economic parameters, including _maxTxAmount, _maxWalletSize, and the bots list (7.5 Governance). This centralization, coupled with the ability to arbitrarily block users or halt trading, presents a significant economic and governance risk.
The contract is not designed with an upgrade mechanism (e.g., proxy pattern) (7.7 Upgrades). This means the contract's logic is immutable once deployed. While this eliminates risks associated with upgradeability (like proxy misconfigurations or malicious upgrades), it also means that any discovered vulnerabilities or desired feature changes cannot be implemented without a new deployment and migration.
It is strongly recommended to decentralize control over critical parameters to mitigate the significant centralization risks identified.
Consider implementing a multi-signature wallet or a time-locked governance mechanism for sensitive functions like setting taxes, transaction limits, and managing bot lists. Thoroughly review the economic parameters, especially initial tax rates and anti-whale limits, to ensure they align with the project's long-term vision and do not inadvertently deter legitimate trading or create a 'honeypot' perception. If ownership is to be renounced, ensure all parameters are set to their final, desired state, and that the community understands the implications of an immutable contract.
Contract & Record
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
- Sep 4, 20267Low
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
Frequently Asked Questions
What is the MOODENG contract address?
The MOO DENG (MOODENG) contract on Ethereum is 0x28561b8a2360f463011c16b6cc0b0cbef8dbbcad. Compare it with the address the project itself publishes before trading: other contracts can carry the same name and ticker.
Is MOO DENG a scam?
Quantum Audit's risk score for MOO DENG is 7/100 (Low risk) as of Sep 4, 2026, computed by a deterministic function from on-chain facts — Contract verified: Verified; Ownership: Renounced; Mint: No mint; Liquidity lock: Locked; Upgradeability: Fixed code; Honeypot: None found; Buy / sell tax: 0% / 0%. A score is a dated snapshot of those facts, not a guarantee; each one is listed on this page.
Is MOODENG liquidity locked?
Liquidity lock: Locked (as of Sep 4, 2026). Total DEX liquidity: $525.0K.
Who holds MOODENG?
As of Sep 4, 2026, the 10 largest holders own 41.7% of the supply. The Holders section on this page shows who they are by holder type.
Would You Like a More Detailed Audit of MOO DENG?
Our AI-powered scanner gives you a deeper, real-time smart contract analysis — free, with every scoring factor shown.
Get Detailed Audit Is this your token? Publish your own audit on this page