Quantum Audit Logo

Is Brain Armstrong Safe?

On-chain security analysis — is it a scam or legit?

Brain Armstrong BRAINARM
0xb200…1d01
Base
Not verifiedThis 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.
Last checked today 1 audit on record
DexScreener ↗
How is this score calculated? → Medium Risk
Executive SummaryAI Copilot

This audit report is based on the provided contract address 0xb2000000000000000000005a0c125da6cf531d01 on the Base network. No Solidity source code was provided for analysis, nor was the contract verified on a block explorer. Therefore, a comprehensive security assessment of the contract's logic, architecture, and potential vulnerabilities could not be performed. The findings are limited to general observations about unverified contracts.

3 Informational
Volume 24h
$137.6K
Liquidity
$64.4K
Price
$0.0002662
Token Age
8d
Top 10 Holders
0.0%

Security Findings

3 Info
Info

Lack of Verified Source Code

I-01The contract at 0xb200…1d01 is not verified on the Base block explorer, meaning its Solidity source code is not publicly available. This significantly hinders transparency and prevents a comprehensive security audit of its internal logic and behavior.
IssueThe contract at is not verified on the Base block explorer, meaning its Solidity source code is not publicly available. This significantly hinders transparency and prevents a comprehensive security audit of its internal logic and behavior.
FixPublish and verify the Solidity source code on the Base block explorer. This allows for public review, enhances trust, and enables security researchers to identify potential vulnerabilities. Ensure that the verified code accurately reflects the deployed bytecode.
StatusUnresolved
Info

Inability to Assess Technical Security

I-02Due to the absence of source code, critical technical security aspects such as reentrancy protection, integer overflow/underflow safeguards, access control mechanisms, and adherence to secure coding practices (e.g., Checks-Effects-Interactions pattern) cannot be evaluated. This leaves the contract's resilience against common attack vectors unknown.
IssueDue to the absence of source code, critical technical security aspects such as reentrancy protection, integer overflow/underflow safeguards, access control mechanisms, and adherence to secure coding practices (e.g., Checks-Effects-Interactions pattern) cannot be evaluated. This leaves the contract's resilience against common attack vectors unknown.
FixOnce source code is available, a thorough technical security audit should be performed to identify and mitigate vulnerabilities related to code security (7.2 Code Security) and access control (7.3 Access Control). Implement robust testing, including unit, integration, and fuzz testing.
StatusUnresolved
Info

Unquantifiable Economic and Governance Risks

I-03Without the contract's source code, it is impossible to analyze its economic model (7.4 Economic), governance structure (7.5 Governance), or interactions with external protocols (7.6 External). This prevents the identification of potential economic exploits (e.g., oracle manipulation, flash loan attacks) or centralized control points that could pose significant risks to users and the protocol's stability.
IssueWithout the contract's source code, it is impossible to analyze its economic model (7.4 Economic), governance structure (7.5 Governance), or interactions with external protocols (7.6 External). This prevents the identification of potential economic exploits (e.g., oracle manipulation, flash loan attacks) or centralized control points that could pose significant risks to users and the protocol's stability.
FixProvide comprehensive documentation and source code to allow for a full assessment of economic and governance risks. Clearly define the contract's role within the broader protocol, its dependencies, and any administrative privileges. Implement robust governance mechanisms where applicable.
StatusUnresolved

Category Ratings

TechnicalMedium6/10

Without access to the Solidity source code (7.2 Code Security), a detailed technical analysis of the contract's architecture (7.1 Architecture), implementation, and potential vulnerabilities is impossible. This significantly elevates the technical risk, as common issues like reentrancy, integer overflows, or access control flaws (7.3 Access Control) cannot be identified. The lack of visibility prevents any assessment of code quality or adherence to secure coding practices.

GovernanceHigh3/10

The economic model (7.4 Economic) and governance mechanisms (7.5 Governance) of the contract cannot be evaluated without source code. This prevents analysis of potential economic exploits, such as flash loan attacks or oracle manipulation, and assessment of centralized control points. The interaction with external contracts (7.6 External) also remains unknown, posing an unquantifiable risk.

UpgradesMedium5/10

Without source code, it is impossible to determine if the contract employs an upgradeable proxy pattern (7.7 Upgrades) or if any upgrade mechanisms are present. This lack of information means that potential upgradeability risks, such as insecure upgrade paths or proxy pattern misconfigurations, cannot be assessed. Furthermore, operational aspects (7.8 Operations) related to upgrades or administrative functions are entirely opaque.

Security Checklist

1/5 checks passed
Contract VerifiedFail
Ownership Renounced?
No Mint Function?
Liquidity LockedFail
Not a ProxyPass

Liquidity Depth

$64.8K across 5 pairs
Uniswap v4ETHanalysed$64.4K99.4%0x7456…0534BG$2100.3%Uniswap v4USDC$1140.2%Uniswap v4USDC$240.0%Uniswap v4USDC$220.0%

The risk score reads depth across every pair. The volume figure and the volume-to-liquidity ratio elsewhere on this page describe only the pair this audit analysed, so the two are not directly comparable.

What Raised This Score

5 factors
  • Ownership status UNKNOWN (owner could not be resolved)
  • Mint capability UNKNOWN (implementation ABI unreadable)
  • Contract source NOT verified
  • Liquidity NOT locked (owner can withdraw — rug-pull risk)
  • Token age < 30 days (still settling)

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

Related Audits

6 more on the record
B3Medium RiskLienFi (LFI)Medium RiskMey Network (MEY)Medium RiskDerive (DRV)Medium RiskVenice Deity (VVVEITY)Medium Risktokenbot (CLANKER)Medium Risk

Would You Like a More Detailed Audit of Brain Armstrong?

Our AI-powered scanner gives you a deeper, real-time smart contract analysis — free, with every scoring factor shown.

Get Detailed Audit