Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

bi-core-bi-core-corenpm

bi-core-bi-core-core is a confirmed malicious npm package (MAL-2026-12829) that steals credentials and exfiltrates sensitive data (malicious version 35.8.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bi-core-bi-core-core (npm)

MAL-2026-12829
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bi-core-bi-core-core

What this malware does

On require() of the package, index.js triggers _compat.js which selects a per-platform binary path, downloads bytes from runtime-assembled oob-worker*.workers.dev Cloudflare Workers hosts (with a DNS TXT fallback via *.dl.wel1.ru subdomains), writes them to /tmp or %TEMP% under disguised names (.cache_<hex>, dotnet_diag_<hex>.exe), chmods 0755, and spawns them detached via /bin/sh -c on Unix or cmd.exe /c start /b on Windows. Mirror hosts, DNS fallback hostnames, and the child_process reference are constructed by joining split string fragments at runtime (e.g. ["oob-work","er.cf100-41",...].join(''), require("child_" + "process")) to defeat static string scans. The package presents itself as a trivial base framework module — index.js contains only a stub class before invoking the dropper — and the name is a duplicated-token typosquat shape (bi-core-bi-core-core) published at an inflated version (35.8.5) with no legitimate functionality.

Malicious versions

1 flagged
35.8.5

Indicators of compromise (SHA-256)

f7a6c642622497cec2ce5317e0e3e7e44f94b3832db9c06e13d336b5387009f1

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bi-core-bi-core-core (version 35.8.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bi-core-bi-core-core across your stack and pipelines.

  2. If you installed it — respond

    bi-core-bi-core-core 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.

  3. Did it already run?

    If bi-core-bi-core-core 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.

  4. How O3 protects you

    O3 blocks bi-core-bi-core-core 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

No. bi-core-bi-core-core on npm has been identified as a malicious package (version 35.8.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015554

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bi-core-bi-core-core-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