NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

api-node-sdknpm

Advisory published Updated

api-node-sdk is a confirmed malicious npm package (MAL-2026-11124) that steals credentials and exfiltrates sensitive data (malicious version 2.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in api-node-sdk (npm)

MAL-2026-11124
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall api-node-sdk

What this malware does

On npm install, the package's postinstall hook (node test.js) executes an attacker-controlled workflow against the installer's host. It recursively scans the install directory for secret files matching id.json, config.toml, Config.toml, env, and .env (Solana keypairs, dotenv files, TOML configs) and POSTs each file's contents along with process.env.USER to http://95.216.118.146:3000/api/v1 over plain HTTP. It then fetches an attacker-supplied SSH public key from http://95.216.118.146:3001/api/ssh-key, appends it to ~/.ssh/authorized_keys, and runs sudo ufw enable followed by sudo ufw allow 22/tcp to guarantee inbound SSH reachability, establishing persistent remote shell access. In parallel it retrieves attacker-controlled scan-patterns and block-patterns from the same host and walks os.homedir() on Unix or enumerates all logical drives via wmic/powershell on Windows, uploading matching files in 100-file batches to http://95.216.118.146:3001/api/v1 with username and platform metadata. Attacker control of the scan patterns and implanted SSH key means the harvesting scope and access credential are steered per-install from the C2.

Malicious versions

1 flagged
2.1.6

Indicators of compromise (SHA-256)

a8133fdea40df12d51091c8ce094062f366f0c30be0d17667a827ed00b75f78a

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for api-node-sdk (version 2.1.6).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-010863

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

api-node-sdk (npm) malicious package — MAL-2026-11124 | O3 Security