Which versions of bingocode are malicious?

The following npm versions of bingocode are flagged malicious: 1.1.123, 1.1.163. Treat any of these as compromised.

How do I remediate bingocode if I installed it?

bingocode 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.

I already installed bingocode — how do I know if it already compromised me?

If bingocode was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is bingocode part of a known attack campaign?

Yes — bingocode is associated with the IN-MAL-2026-004149, IN-MAL-2026-005809 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find bingocode across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bingocode (2 malicious versions).

Malicious package

bingocodenpm

Advisory published May 22, 2026Updated Jun 12, 2026

bingocode is a confirmed malicious npm package (MAL-2026-4497) that steals credentials and exfiltrates sensitive data (malicious versions 1.1.123, 1.1.163). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bingocode (npm)

MAL-2026-4497

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bingocode

What this malware does

The package declares bin.claude pointing at bin/claude-win.cjs (and bin/claude on Linux/macOS). After npm i -g bingocode, the claude command on PATH is this package, not Anthropic's official @anthropic-ai/claude-code. On first invocation, each bin script runs deployBingoDefaults() which copies config/bingo-defaults/settings.json into ~/.claude/bingo/settings.json; the shipped settings pin ANTHROPIC_BASE_URL to http://127.0.0.1:3456 and the package's .env.example documents routing prompts through MiniMax / OpenRouter / DeepSeek backends. The net effect: a user who types claude expecting Anthropic's CLI gets their prompts (and any associated auth) silently brokered through a local proxy under this package's control, then forwarded to author-chosen LLM providers. The npm postinstall hook (scripts/install-skills.cjs) additionally copies bundled skill directories into ~/.claude/skills/ (Anthropic Claude's user-config namespace), giving this package script-level influence over the sibling tool's behavior. On Linux/macOS, bin/claude also runs npm install -g bun at first invocation if bun is missing — privileged global install without explicit consent, though the package fetched is pinned-by-name from the public npm registry. The combination of bin-name hijack + seeded settings redirecting the API base URL is the silent-relay shape: caller-supplied prompts route to a destination the caller did not choose. The YARA js_network_command_exfiltration hits on src/bridge/bridgeMain.ts, src/services/mcp/*, src/utils/hooks/execHttpHook.ts, etc. are pattern-matches on code vendored from Anthropic's open-source Claude Code (bridge poll loops, MCP client, SSRF-guarded http-hook with URL allowlist) and do not represent installer-harm behavior on their own.

Malicious versions

2 flagged

1.1.1231.1.163

Indicators of compromise (SHA-256)

7bb3ff21cce9379a60d3ebe3408d8c179e39cfd940eed6deb4afb2f28d852254

78f3d873e7c4d16629263bb242a2636f18747d5dd096b614fb3cf43a56d2dc8e

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for bingocode (2 malicious versions).
If you installed it — respond
bingocode 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 bingocode was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bingocode on npm has been identified as a malicious package (versions 1.1.123, 1.1.163 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004149IN-MAL-2026-005809

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bingocode-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database