MalwarePublished 13 Jul 2026

abuden2 (npm) · Malicious Code

Affects abuden2Source GCVE Database

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

Data as of 26 Oct 2026, 15:56 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-10252

What to do

Remove abuden2 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
npmabuden2	Affected =2.0.0 =1.1.7 =1.7.7	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 'abuden2' contains malicious code that fully compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected machine should be rotated immediately from a different, trusted device. Removing the package alone does not guarantee removal of all malicious software introduced by the package.

Impact

Full compromise of any computer with the 'abuden2' package installed or running. Potential loss of confidentiality, integrity, and availability of data on the affected system. All secrets and keys stored on the machine are considered exposed and must be rotated. The system may remain compromised even after removal of the package.

Defensive guidance

Immediately remove the 'abuden2' package from affected systems. Rotate all secrets and keys stored on the compromised machine from a separate, trusted device. Conduct a thorough investigation and remediation of the affected system to identify and remove any persistent malicious software. Due to the severity of the compromise, consider rebuilding the system from a known good backup if possible.

Summary

The 'abuden2' package in the npm ecosystem is identified as containing malicious code that results in a full system compromise upon installation or execution. This level of compromise implies that attackers may gain complete control over the affected system. Due to the severity, all sensitive credentials stored on the compromised machine must be rotated from a secure environment. The package removal is necessary but insufficient to fully remediate the infection, as persistent malicious components may remain.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Jul 2026, 09:40 UTC

Technical details

References

Community reviews