MalwarePublished 11 Jun 2026Updated 8 Jul 2026

downlynpm (npm) · Malicious Code

Affects downlynpmSource GCVE Database

Malicious package : remove downlynpm and rotate any secrets on hosts that installed it.

Data as of 9 Jul 2026, 09:55 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-5666

What to do

Remove downlynpm from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmdownlynpm	Affected =1.0.0 =1.0.2 =1.0.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package 'downlynpm' versions 1.0.0, 1.0.1, and 1.0.2 contains malicious code or depends on a package with malicious code. Installing or running this package can lead to full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different, secure machine. Removing the package alone may not fully remove the malicious software or undo the compromise.

Impact

Systems with the affected versions of 'downlynpm' installed or running should be considered fully compromised. Attackers may have gained full control over the system, potentially exposing all stored secrets and keys. This can lead to further unauthorized access, data theft, or persistence of malicious software beyond the presence of the package itself.

Defensive guidance

Immediate removal of the 'downlynpm' package versions 1.0.0, 1.0.1, and 1.0.2 is recommended. Additionally, all secrets and keys stored on the compromised system should be rotated immediately from a different, secure computer. Because the system may remain compromised even after removal, consider rebuilding or thoroughly cleaning the affected system to ensure complete eradication of the malicious code.

Summary

The 'downlynpm' package in the npm ecosystem, specifically versions 1.0.0, 1.0.1, and 1.0.2, has been identified as containing malicious code or consuming a dependency that contains malicious code. This malicious code can lead to a full compromise of any computer where the package is installed or running. The compromise includes potential unauthorized access to secrets and keys stored on the system. Due to the nature of the compromise, simply uninstalling the package may not be sufficient to remove all malicious artifacts or control established by the attacker.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2026, 09:55 UTC

Technical details

References

Community reviews