T05 · Unauthorized Access and Privilege Escalation
- Location
pumpbets.json:265- Finding
Privileged Emergency Withdrawal Can Precede the Advertised Claim Period
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent PumpMarket betting skill, but it enables agent-driven real-SOL mainnet betting and exposes a privileged emergency withdrawal path that users should review carefully.
Install only if you understand that this skill can help an agent spend real SOL on mainnet. Use a dedicated wallet with limited funds, require explicit approval before every createMarket or placeBet transaction, pin dependencies, simulate first, and review the program's emergency withdrawal behavior before depositing meaningful funds.
pumpbets.json:265Privileged Emergency Withdrawal Can Precede the Advertised Claim Period
skill.md:104Security-Sensitive Runtime Dependencies Are Installed Without Version Pinning
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
# Verify API is healthy
curl -s https://pumpbet-mainnet.up.railway.app/api/health | python3 -m json.tool
# Verify program on-chain (requires solana CLI)
solana program show 3mNbBV3Xc3rNJ4E87pSFzW7VhUZySHQDQVyd4MP2VFG6 --url mainnet-beta
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
solana balance 4iFYGzxKGH2SAeVaR5AxPiCfLCSQD9fdPK8tsDBbmx3f --url mainnet-beta
curl -s https://pumpbet-mainnet.up.railway.app/api/stats | python3 -m json.tool
### Reproduce Account Counts via RPC
The manifest description frames the skill as a prediction/betting capability for pump.fun token graduations, but this IDL exposes an additional administrative fund-recovery path via emergencyWithdraw. That goes beyond merely facilitating predictions and includes a privileged asset-seizure/recovery mechanism over market funds.
The IDL exposes an emergencyWithdraw path where only a generic signer authority and arbitrary recipient are visible at the interface level, while the docs claim this is treasury-only and delayed. If the on-chain implementation fails to strictly enforce that authority equals the official treasury and that the time delay and recipient constraints are met, this becomes a direct fund-drain path from the vault.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
import { Keypair } from '@solana/web3.js'; import fs from 'fs';
// Ensure keyfile permissions: chmod 600 ~/.config/solana/id.json const secret = JSON.parse(fs.readFileSync(process.env.KEYPAIR_PATH!, 'utf-8')); const keypair = Keypair.fromSecretKey(Uint8Array.from(secret));
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
import { Keypair } from '@solana/web3.js'; import fs from 'fs';
// Ensure keyfile permissions: chmod 600 ~/.config/solana/id.json const secret = JSON.parse(fs.readFileSync(process.env.KEYPAIR_PATH!, 'utf-8')); const keypair = Keypair.fromSecretKey(Uint8Array.from(secret));
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
PID=3mNbBV3Xc3rNJ4E87pSFzW7VhUZySHQDQVyd4MP2VFG6
count_by_size () {
curl -s $RPC -X POST -H 'Content-Type: application/json' -d "{
\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"getProgramAccounts\",
\"params\":[\"$PID\",{
\"encoding\":\"base64\",
The skill explicitly recommends an automated loop that can place bets and submit claim transactions on Solana mainnet using real SOL, but it does not require an explicit user confirmation or spending guard before each transaction. In an agent context, this creates a real risk of autonomous financial loss because the agent is instructed to discover markets, act on signals, and submit on-chain transactions without a human approval checkpoint.
This JSON manifest contains natural-language instruction docs such as "Create a new prediction market for a pump.fun token" but provides no explicit trigger phrases, activation scope, or exclusion conditions. In a manifest file, that can make skill invocation criteria ambiguous because the descriptions read like general capability statements rather than narrowly scoped triggers.