Quantum Audit Logo
Launch App

Is Palantir Technologies Inc. Safe?

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

Palantir Technologies Inc. PLTRC
0xb200…abbe
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
How is this score calculated? → Medium Risk
Executive SummaryAI Copilot

This audit was conducted without access to the contract's source code. The contract at 0xb2000000000000000000007d16372840df4dabbe on the Base network is unverified. Without the source code, a comprehensive security analysis is impossible, and all associated risks are significantly elevated. Users are strongly cautioned against interacting with unverified contracts.

1 Critical2 High4 Informational
Volume 24h
$3.30M
Liquidity
$703.7K
Price
$208.0079
Token Age
12d
Top 10 Holders
0.0%

Security Findings

Critical

Unverified Contract Source Code

C-01The contract at address 0xb200…abbe on the Base network does not have its source code verified on the block explorer. This prevents any form of security analysis, including identifying common vulnerabilities like reentrancy, access control flaws, or logical errors. Users cannot independently verify the contract's intended functionality or safety.
IssueThe contract at address on the Base network does not have its source code verified on the block explorer. This prevents any form of security analysis, including identifying common vulnerabilities like reentrancy, access control flaws, or logical errors. Users cannot independently verify the contract's intended functionality or safety.
FixThe contract deployer should immediately publish and verify the full source code on the Base block explorer. Without verified source code, users should treat this contract as highly risky and avoid any interaction.
StatusUnresolved
High

Unknown Contract Functionality and Intent

H-01Without verified source code, the exact functionality, purpose, and intended behavior of the contract are completely unknown. This lack of transparency means that the contract could contain malicious logic, such as backdoors, rug pull mechanisms, or arbitrary token transfers, posing an extreme risk to any funds or assets sent to or managed by it. (7.2 Code Security, 7.4 Economic)
IssueWithout verified source code, the exact functionality, purpose, and intended behavior of the contract are completely unknown. This lack of transparency means that the contract could contain malicious logic, such as backdoors, rug pull mechanisms, or arbitrary token transfers, posing an extreme risk to any funds or assets sent to or managed by it. (7.2 Code Security, 7.4 Economic)
FixUsers should exercise extreme caution. Do not send any assets or approve any transactions with this contract until its functionality is fully understood and verified through published source code and a security audit.
StatusUnresolved
High

Inability to Assess Upgradeability and Operational Risks

H-02The absence of source code makes it impossible to determine if the contract is upgradeable, what proxy pattern (if any) is used, or who controls potential upgrade mechanisms. This introduces significant operational risks (7.8 Operations) as the contract's logic could be changed at any time without public notice, potentially introducing new vulnerabilities or malicious functionality. (7.7 Upgrades)
IssueThe absence of source code makes it impossible to determine if the contract is upgradeable, what proxy pattern (if any) is used, or who controls potential upgrade mechanisms. This introduces significant operational risks (7.8 Operations) as the contract's logic could be changed at any time without public notice, potentially introducing new vulnerabilities or malicious functionality. (7.7 Upgrades)
FixIf the contract is intended to be upgradeable, the proxy and implementation contracts must both have verified source code. All upgrade mechanisms and associated access controls should be clearly documented and audited. Without this, assume the contract's logic can change unpredictably.
StatusUnresolved
Info

Listed, but not independently verified

QA-IDENTITYListed on CoinGecko as Palantir (Coinbase Tokenized Stock) (PLTRC), rank #3347.
IssueListed on CoinGecko as Palantir (Coinbase Tokenized Stock) (PLTRC), rank #3347.
FixMatch the contract address against the project's official channels before trading.
StatusAcknowledged
Info

The market for this token

QA-MARKETLiquidity $709K (DexScreener, all pools). 24h trading volume $3.1M (CoinGecko, all markets, daily snapshot). 24h trading volume $3.3M (DexScreener, all pools).
IssueLiquidity $709K (DexScreener, all pools). 24h trading volume $3.1M (CoinGecko, all markets, daily snapshot). 24h trading volume $3.3M (DexScreener, all pools).
FixSize any position to the liquidity and daily volume shown — they set how much you can sell and at what price.
StatusAcknowledged
Info

Asset class: Tokenized real-world asset

QA-PROFILEA token backed by an off-chain asset (a stock, gold, treasury bills, a fund share) held by a named issuer or custodian. Issuance, redemption and transfer restrictions are the issuer's by design. The class itself adds no points; the contract and market facts decide the score. Basis: CoinGecko category: Tokenized Stocks. Tokenomics — Supply: mint capability could not be read. Control: an owner that could not be resolved. Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $709K of DEX liquidity across 5 pools. Launch: 12 days of market history.
IssueA token backed by an off-chain asset (a stock, gold, treasury bills, a fund share) held by a named issuer or custodian. Issuance, redemption and transfer restrictions are the issuer's by design. The class itself adds no points; the contract and market facts decide the score. Basis: CoinGecko category: Tokenized Stocks. Tokenomics — Supply: mint capability could not be read. Control: an owner that could not be resolved. Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $709K of DEX liquidity across 5 pools. Launch: 12 days of market history.
FixTreat the issuer or custodian as the counterparty: check its custody reports and who may hold or redeem the token.
StatusAcknowledged
Info

Recently launched — 12 days of market history

QA-RECENTThe token's oldest DEX pool is 12 days old. Age is not part of the risk score — a new token is not a risky one by default — but a short history means fewer trades and holder changes behind the facts in this report.
IssueThe token's oldest DEX pool is 12 days old. Age is not part of the risk score — a new token is not a risky one by default — but a short history means fewer trades and holder changes behind the facts in this report.
FixRe-check ownership, liquidity and holder distribution as the token matures; those are the facts that move early.
StatusAcknowledged

Category Ratings

TechnicalMedium6/10

Without access to the contract's source code, a comprehensive technical security analysis (7.1 Architecture, 7.2 Code Security, 7.3 Access Control) is not possible. This significantly elevates the technical risk as common vulnerabilities like reentrancy or integer overflows cannot be identified. For example, the absence of verified code prevents scrutiny of internal logic and state transitions, making it impossible to assess the correctness of critical functions or identify potential backdoors.

GovernanceHigh3/10

The economic and governance aspects (7.4 Economic, 7.5 Governance) cannot be evaluated without the contract's implementation details. It is impossible to determine if there are any economic attack vectors, such as flash loan vulnerabilities or oracle manipulation, or if governance mechanisms are robust. For instance, the presence of privileged roles or potential for rug pulls remains unknown, posing a significant risk to user funds and protocol stability.

UpgradesMedium5/10

The upgradeability status and associated risks (7.7 Upgrades) are entirely unknown without the source code. It is impossible to determine if the contract is upgradeable, what proxy pattern (e.g., UUPS, Transparent) might be in use, or if upgrade mechanisms are secure. This lack of transparency means potential backdoors or future malicious changes cannot be assessed, presenting a critical operational risk (7.8 Operations) to users.

Security Checklist

Contract VerifiedFail
Ownership Renounced?
No Mint Function?
Liquidity LockedFail
Not a ProxyPass

Liquidity Depth

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

  • Mint capability UNKNOWN (implementation ABI unreadable)
  • Ownership status UNKNOWN (owner could not be resolved)
  • Liquidity NOT locked (100% of the pool; this pool is 99% of DEX liquidity) — who holds it cannot be verified
  • Contract source NOT verified — its logic cannot be read

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

Jito Staked SOL (JITOSOL)Medium RiskDolphin (POD)Medium Risk0xAgentEVE (EVE)Medium RiskWELLMedium RiskBittensor (TAO)Medium RiskVelvetMedium Risk

Would You Like a More Detailed Audit of Palantir Technologies Inc.?

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

Get Detailed Audit