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

lazyhtml-scriptsnpm

Malicious code in lazyhtml-scripts (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3331
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall lazyhtml-scripts

What this malware does

The package lazyhtml-scripts was found to contain malicious code.

The OpenSSF Package Analysis project identified 'lazyhtml-scripts' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

71844816af603d74c0b28463789c32032f49ba227282ce2b9a735ecc9438bace
45abfd9582509b7e6ded4a7ce678a25aef82365186bba18330d6f76f1cf3c5ea

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for lazyhtml-scripts (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lazyhtml-scripts across your stack and pipelines.

  2. If you installed it — respond

    Remove lazyhtml-scripts from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

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

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks lazyhtml-scripts-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

lazyhtml-scripts (npm) malicious package — MAL-2026-3331 | O3 Security