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

secp256k1-libnpm

secp256k1-lib is a confirmed malicious npm package (MAL-2026-14255) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in secp256k1-lib (npm)

MAL-2026-14255
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall secp256k1-lib

What this malware does

Package name mimics the widely used secp256k1 cryptography library but contains no cryptographic functionality. The declared main (index.js) is a single 33KB obfuscator.io-packed bundle whose only readable tokens are require( and axios; all strings — including target hostnames, URLs, and function names — are hex-escaped entries in the _0x4058 string array that are reconstructed at runtime. README is 24 bytes and the package description (logger tool for validation entry) does not match a secp256k1 implementation. On require('secp256k1-lib') the obfuscated bundle executes and instantiates an HTTP client (axios) targeting a runtime-constructed destination that could not be recovered from the shipped bytes. Shape matches a credential/wallet-stealer loader: name confusion with a high-value crypto package + no legitimate functionality + obfuscated import-time network capability with a hidden destination.

Malicious versions

4 flagged
1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

17719ed10229a405c54b60369c8c567a5964f6613aec21ead50e0d4eccb37104
57d7b119d3510a8e00d57da8b51c023a77f4133008a24fed5e4644d4cf5d353e
8e9ffe9aa6410c78f18aa4a432419b77539b2bb1fc893896ae00f3cc22f6d26d
dd45f2520f57a18e182ea26170f8d6d3b4296929c66dbbf2ea0eb632adb1f46a

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for secp256k1-lib (4 malicious versions).

  2. If you installed it — respond

    secp256k1-lib 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 secp256k1-lib 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. secp256k1-lib on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 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-018366IN-MAL-2026-018363IN-MAL-2026-018364IN-MAL-2026-018365

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks secp256k1-lib-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

secp256k1-lib (npm) malicious package — MAL-2026-14255 | O3 Security