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

idlive-document-capture-webnpm

Malicious code in idlive-document-capture-web (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10733
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall idlive-document-capture-web

What this malware does

Package name typosquats the legitimate 'idlive' family and ships no library functionality. package.json declares a preinstall lifecycle hook ("preinstall": "node index.js") that auto-executes on npm install. index.js collects host reconnaissance — hostname, platform, arch, username, uid/gid, shell, homedir, cwd, and the output of whoami/id spawned via child_process — and POSTs the collected data as JSON to the hardcoded attacker-controlled endpoint https://koc9471aou79yxauab6in903uu0locc1.oastify.com/detox56. The oastify.com host is Burp Suite Collaborator, an out-of-band interaction service commonly used as an exfiltration sink. There is no legitimate purpose for this behavior; the package exists solely to beacon installer-side identifiers to the attacker's OAST subdomain at install time.

Malicious versions

1 flagged
14.2.1

Indicators of compromise (SHA-256)

d428a1956dd86e85bfb6fb83cba2dea11bfc19250c1262d13a88c3bdd8ca07e0

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

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-010720

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks idlive-document-capture-web-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

idlive-document-capture-web (npm) malicious package — MAL-2026-10733 | O3 Security