Which versions of cdnhost are malicious?

The following npm versions of cdnhost are flagged malicious: 0.0.1-security. Treat any of these as compromised.

How do I remediate cdnhost if I installed it?

Remove cdnhost 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.

I already installed cdnhost — how do I know if it already compromised me?

If cdnhost was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is cdnhost part of a known attack campaign?

Yes — cdnhost is associated with the GHSA-wh7m-vhx9-f4qq 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 cdnhost across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cdnhost (version 0.0.1-security).

Malicious package

cdnhostnpm

Advisory published Jan 28, 2026Updated Feb 2, 2026

cdnhost is a confirmed malicious npm package (MAL-2026-550) that executes malicious code on install (malicious version 0.0.1-security). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cdnhost (npm)

MAL-2026-550

Immediate action

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

npm uninstall cdnhost

What this malware does

The package cdnhost 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.

Malicious versions

1 flagged

0.0.1-security

Indicators of compromise (SHA-256)

e0181f4fe287a7879047e64112250e5009c28564cf6017ad1d2f966e706da109

dacea96d573c773c7dab188922e5a1bd655ff37114ebcee7c23d1415bc4dc4ef

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for cdnhost (version 0.0.1-security).
If you installed it — respond
Remove cdnhost 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.
Did it already run?
If cdnhost was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. cdnhost on npm has been identified as a malicious package (version 0.0.1-security flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wh7m-vhx9-f4qq

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database