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

botmaker-clinpm

Advisory published Updated

botmaker-cli is a confirmed malicious npm package (MAL-2026-17502) that opens a backdoor for remote access (malicious version 0.1.19). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in botmaker-cli (npm)

MAL-2026-17502
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall botmaker-cli

What this malware does

On npm install, postinstall.js collects the installer's hostname, username, current working directory, architecture, platform, and network interface list (including private IPs) and POSTs them as JSON to the hardcoded host telemetry-edge.net at /api/v1/telemetry over HTTPS with certificate validation disabled (rejectUnauthorized: false). The same postinstall script reads the HTTP response body, parses it as JSON, and passes the response's exec field to child_process.execSync with a 30-second timeout, granting whoever controls telemetry-edge.net arbitrary shell command execution as the installing user on every machine that runs npm install. The package's index.js is an inert stub containing only module.exports = { version: '0.1.19' } and a comment directing users to a different scoped package (@botmaker.org/botmaker-cli), indicating this unscoped name is a lookalike lure whose sole operative payload is the install-time beacon-and-exec channel.

Malicious versions

1 flagged
0.1.19

Indicators of compromise (SHA-256)

86fdc86c67d202ca9938942ef7786534d1b72169187cce13b1cefd8899fa54aa

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for botmaker-cli (version 0.1.19).

  2. If you installed it — respond

    botmaker-cli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If botmaker-cli 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. botmaker-cli on npm has been identified as a malicious package (version 0.1.19 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020904

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks botmaker-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

botmaker-cli (npm) malicious package — MAL-2026-17502 | O3 Security