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

process-live-lognpm

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

Malicious code in process-live-log (npm)

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

What this malware does

The default export getPlugin issues an HTTPS request to the hardcoded bare-IP endpoint https://31.97.137.157:45000/icons/107 and passes the returned data.credits field to new Function(...) with require, process, Buffer, and other Node globals injected, then invokes it. Any consumer that imports and calls the default export executes attacker-controlled JavaScript with full Node privileges. Package identity is inconsistent: README describes a live-log utility, package.json.description advertises a 'TypeScript SDK for the Polymarket CLOB API', and keywords are ['react','helper','svg']. A dead setDefaultModule function constructs plausible cdnjs URLs but is never called, while the reachable code path targets the bare IP. Declared dependencies (@primno/dpapi, better-sqlite3, node-machine-id) are consistent with browser-credential-stealer post-exploitation tooling the fetched payload could invoke.

Malicious versions

1 flagged
11.5.2

Indicators of compromise (SHA-256)

5a36d35f64443b9dc4a2395017b8738562a321c9765089f916eeebdf58281d57

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

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-017649

References

Credits

  • Amazon Inspector · finder

Detect & block this

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