Which versions of web-types-htmx are malicious?

The following npm versions of web-types-htmx are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate web-types-htmx if I installed it?

web-types-htmx 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.

I already installed web-types-htmx — how do I know if it already compromised me?

If web-types-htmx 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.

Is web-types-htmx part of a known attack campaign?

Yes — web-types-htmx is associated with the GHSA-958x-98wv-7f7j campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find web-types-htmx across my projects, lockfiles, and CI pipelines?

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

Malicious package

web-types-htmxnpm

Malicious code in web-types-htmx (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191153

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall web-types-htmx

What this malware does

The package web-types-htmx was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

07877f867a5e18001cab22b77adf1b5bf737045f63a8ba9a2471208dde03f072

33291d918b3035975214c3b2109bb5f5554ef58b2d0283b826a1e0637471d6c7

999540b3b5a1066e399c44ecf2f220a5318cdea88dea33416c1a3c55bcf80fb7

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for web-types-htmx (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging web-types-htmx across your stack and pipelines.
If you installed it — respond
web-types-htmx 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.
Did it already run?
If web-types-htmx 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.
How O3 protects you
O3 blocks web-types-htmx 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. web-types-htmx on npm has been identified as a malicious package (version 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-958x-98wv-7f7j

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks web-types-htmx-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