wallet-agent-ai-radixnpm
Malicious code in wallet-agent-ai-radix (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
dist/agent.js contains a hardcoded Telegram Bot API endpoint (https://api.telegram.org) reached via fetch() with a POST body that includes values from process.env. The bundle co-references wallet-related endpoints (api.astrolescent.com) alongside the Telegram exfiltration channel. A package whose advertised purpose is wallet/agent functionality has no legitimate reason to POST environment data or wallet context to a hardcoded third-party Telegram bot — this is the canonical hardcoded-C2 exfiltration shape, where any installer/operator running this package leaks data to the attacker who controls the embedded bot token.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for wallet-agent-ai-radix (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wallet-agent-ai-radix across your stack and pipelines.
If you installed it — respond
wallet-agent-ai-radix is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If wallet-agent-ai-radix was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks wallet-agent-ai-radix before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks wallet-agent-ai-radix-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.