Quantum Audit Logo

Is Amazon.com Inc. Safe?

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

Amazon.com Inc. AMZNC
0xb200…c2e8
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 5d ago 1 audit on record
DexScreener ↗
How is this score calculated? → Medium Risk
Executive SummaryAI Copilot

This audit was conducted without access to the smart contract's source code. The provided contract address 0xb200000000000000000000d9192b6b456483c2e8 on the Base network is unverified. Without the source code, a comprehensive security analysis for vulnerabilities such as reentrancy, access control issues, or economic exploits is impossible. The findings are limited to observations based on the lack of transparency and general security best practices.

3 Informational
Volume 24h
$3.07M
Liquidity
$1.00M
Price
$249.2600
Token Age
1y
Top 10 Holders
0.0%

Security Findings

3 Info
Info

Source Code Not Provided for Audit

I-01The source code for the contract at address 0xb200…c2e8 was not provided for this audit. This prevents any meaningful analysis of the contract's logic, security vulnerabilities (7.2), access control (7.3), or economic model (7.4).
IssueThe source code for the contract at address was not provided for this audit. This prevents any meaningful analysis of the contract's logic, security vulnerabilities (7.2), access control (7.3), or economic model (7.4).
FixAlways provide the full, deployable source code for all contracts intended for audit. This is a fundamental requirement for a comprehensive security review.
StatusUnresolved
Info

Contract Not Verified on Block Explorer

I-02The contract at 0xb200…c2e8 is not verified on the Base blockchain explorer. This means the deployed bytecode cannot be directly matched to human-readable source code, hindering transparency and independent verification by users and auditors alike.
IssueThe contract at is not verified on the Base blockchain explorer. This means the deployed bytecode cannot be directly matched to human-readable source code, hindering transparency and independent verification by users and auditors alike.
FixVerify the contract's source code on the Base block explorer (e.g., Basescan). This enhances transparency and allows users to inspect the contract's logic, which is a critical security best practice.
StatusUnresolved
Info

Lack of Transparency and Auditability

I-03The absence of source code and verification on the block explorer severely impacts the transparency and auditability of the contract (7.1). Users cannot independently confirm the contract's intended functionality, potential risks, or adherence to security standards. This creates a significant trust barrier.
IssueThe absence of source code and verification on the block explorer severely impacts the transparency and auditability of the contract (7.1). Users cannot independently confirm the contract's intended functionality, potential risks, or adherence to security standards. This creates a significant trust barrier.
FixPrioritize transparency by publishing and verifying all contract source code. This builds trust within the community and facilitates independent security reviews, which are crucial for the long-term health and security of any decentralized application.
StatusUnresolved

Category Ratings

TechnicalMedium6/10

Due to the absence of the contract's source code, a technical assessment of its architecture (7.1), code security (7.2), and access control mechanisms (7.3) could not be performed. This significantly limits the ability to identify common vulnerabilities like reentrancy, integer overflows, or unauthorized access. Without code, no specific strengths or weaknesses can be identified.

GovernanceHigh3/10

The economic (7.4) and governance (7.5) aspects of the contract could not be evaluated without access to the source code. This prevents analysis of tokenomics, fee structures, potential for oracle manipulation, or governance mechanisms. External dependencies (7.6) and their associated risks also remain unknown.

UpgradesMedium5/10

Without the contract's source code, it is impossible to determine if it employs an upgradeable proxy pattern (7.7) or if any upgradeability mechanisms are present. Consequently, an assessment of upgrade safety, potential for upgrade-related vulnerabilities, or operational risks (7.8) cannot be made. The current state offers no insight into future maintainability or adaptability.

Security Checklist

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

Liquidity Depth

$1.01M across 7 pairs
AerodromeUSDCanalysed$1.00M98.6%Uniswap v3USDC$12.0K1.2%Uniswap v4USDC$2.1K0.2%Uniswap v4ETH$2270.0%Uniswap v4USDC$1000.0%Uniswap v4USDT$10.0%
Show 1 more pairShow less
Uniswap v4USDC$00.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

4 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)

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
OWBMedium RiskFlowerMedium RiskStrategy Inc. (MSTRC)Medium RiskBitVault Signal (BV7X)Medium RiskMoltbook (MOLT)Medium RiskKellyClaudeMedium Risk

Would You Like a More Detailed Audit of Amazon.com Inc.?

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

Get Detailed Audit