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

bjs-lint-buildernpm

Malicious code in bjs-lint-builder (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2880
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bjs-lint-builder

What this malware does

big.js typosquat campaign - SSH backdoor implantation, credential and crypto wallet theft

The package bjs-lint-builder was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

de4578f36842f930e2a5e6a4129c10eb87bf1005fe8cbdf05ffb9fdc2fe43ad8

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 bjs-lint-builder (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bjs-lint-builder across your stack and pipelines.

  2. If you installed it — respond

    bjs-lint-builder 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 bjs-lint-builder 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 bjs-lint-builder 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. bjs-lint-builder on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder
  • SafeDep · finder

Detect & block this

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

bjs-lint-builder (npm) malicious package — MAL-2026-2880 | O3 Security