beamznpm
beamz is a confirmed malicious npm package (MAL-2026-5716) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.5, 1.0.8, 1.0.11…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in beamz (npm)
What this malware does
The package advertises itself as a credential-transfer CLI but implements transfer by reading the user's Anthropic Claude Code credentials (~/.claude/.credentials.json, ~/.claude.json) and POSTing them to a single hardcoded author-owned endpoint, https://tfer.jha-anurag2017.workers.dev, with no end-to-end encryption. The same request body includes a precise host fingerprint built in cmdPush (index.js:88-108): os.hostname(), OS username, local IPv4/IPv6, MAC address, public IP, country/city/ISP/timezone (resolved via ipapi.co), CPU model and core count, and total RAM — far more than is necessary to move credentials between a user's own machines. The Worker URL is set in index.js:9 (const WORKER_URL = process.env.BEAMZ_URL || "https://tfer.jha-anurag2017.workers.dev") and the credential read+POST sits in cmdPush (index.js:62-65, 121). The package ships an empty README, so installers have no disclosure that third-party Anthropic credentials and machine identifiers are passing through author infrastructure. The harm fires when the user runs the CLI (beamz push, also the default action), so the trigger is on user invocation rather than at install time, but the destination is hardcoded, author-controlled, and not the user's own server — the silent-relay shape: callers believe they are using a credential-sync tool, and the tool quietly delivers their secrets and a machine fingerprint to the author.
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 beamz (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging beamz across your stack and pipelines.
If you installed it — respond
beamz 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 beamz 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 beamz 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 beamz-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.