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

btd-smartnpm

btd-smart is a confirmed malicious npm package (MAL-2026-4501) that typosquats a legitimate package to trick installs (malicious versions 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in btd-smart (npm)

MAL-2026-4501
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall btd-smart

What this malware does

The package presents itself as a clone of juliangruber/balanced-match (stolen author identity 'Julian Gruber [email protected]', verbatim README, identical API renamed btdSmart, placeholder homepage 'github.com/your-org/btd-smart'). Appended to the legitimate code in index.js is an obfuscated block that runs unconditionally when the module is required. A custom string-shuffle decoder reconstructs the identifier 'constructor' (and other strings) without any literal occurrences in the file, retrieves the Function constructor from a string prototype, builds a function from a decoded source body, and invokes it. Before invocation, the code stashes require and module onto global under decoder-produced keys so the Function-built code — which otherwise has no closure scope — gains filesystem, network, and process capabilities. The payload body is opaque (deterministic numerical shuffle with 0x7F-based escape tricks across two nested decoders), executes on every require('btd-smart'), and the legitimate balanced-match code above it has no obfuscation, confirming the appended block is purposefully hidden. Combined signals — typosquat with stolen identity, custom obfuscator, dynamic Function eval of a decoded blob at module load, deliberate global-smuggling of require/module — match the documented active-attack shape; no legitimate brace-matching utility needs any of these mechanisms.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged
1.0.21.0.3

Indicators of compromise (SHA-256)

3ad22b27351879a89349a1232ee5abb46bc589399ea710b9769526a8080b3199
f99fec295e7e47a66efd1ddfef051e13f25e9139473356d8a79c1c1d612e2887
8edce8a8e04e183f3bd29cb37d2f3916debf1ebd05c0cbe50fb5f1920f2fa932

Detection & response playbook

Typosquat
  1. Find it

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

  2. If you installed it — respond

    btd-smart is a typosquat — you almost certainly intended a legitimately-named package. Remove btd-smart, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If btd-smart 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 btd-smart 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. btd-smart on npm has been identified as a malicious package (versions 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003259IN-MAL-2026-003250GHSA-m4m6-q4p8-3vjv

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks btd-smart-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

btd-smart (npm) malicious package — MAL-2026-4501 | O3 Security