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

external-process-live-lognpm

external-process-live-log is a confirmed malicious npm package (MAL-2026-13949) that steals credentials and exfiltrates sensitive data (malicious version 13.5.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in external-process-live-log (npm)

MAL-2026-13949
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall external-process-live-log

What this malware does

The package's default export issues an HTTPS request to the hardcoded bare-IP endpoint https://31.97.137.157:45000/icons/107 (with a 'bearrtoken: logo' header and a font-awesome-styled path used as cover) and passes the response's credits field into a new Function('require','module',...,'Promise', data.credits) constructor, executing attacker-supplied JavaScript with full Node context on the consumer's host. The package.json describes the module as a 'TypeScript SDK for the Polymarket CLOB API' and declares unused dependencies associated with credential access on Windows (@primno/dpapi, node-machine-id, better-sqlite3, socket.io-client) that index.js never references; a setDefaultModule helper fabricates a plausible CDN-style URL string that is not actually used, serving as cover for the bare-IP fetch. The package name and README frame the module as a simple process logger, which conflicts with both the declared Polymarket SDK metadata and the observed remote-execution behavior.

Malicious versions

1 flagged
13.5.2

Indicators of compromise (SHA-256)

e3b21f410276a5ec436e583a1b0c08aab7f5f977f3868fd742c7a05ab0197751

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 external-process-live-log (version 13.5.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging external-process-live-log across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-017664

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks external-process-live-log-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database