MalwarePublished 13 Jul 2026

abuden225 (npm) · Malicious Code

Affects abuden225Source GCVE Database

Malicious package : remove abuden225 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-10266

What to do

Remove abuden225 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
npmabuden225	Affected =1.1.7 =2.0.0 =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 'abuden225' contains malicious code that fully compromises any computer on which it is installed or running. The presence of this package indicates a complete system compromise, and all secrets and keys stored on the affected machine should be rotated immediately from a separate, secure device. Removing the package alone does not guarantee removal of all malicious software introduced by it.

Impact

Full system compromise on any computer with the 'abuden225' package installed or running. This includes potential unauthorized access, control, and exfiltration of sensitive information such as secrets and keys. The integrity and confidentiality of the affected system cannot be trusted after installation.

Defensive guidance

Immediately remove the 'abuden225' package from affected systems. Rotate all secrets and keys stored on the compromised computer from a separate, secure device. Because the system is fully compromised, consider rebuilding the system from a known good backup or reinstalling the operating system to ensure complete removal of malicious components.

Summary

The 'abuden225' package in the npm ecosystem is identified as malicious software that, once installed or executed, results in full compromise of the host system. This includes potential unauthorized access and control by an external entity. Due to the severity of the compromise, secrets and keys stored on the affected system must be rotated from a different, uncompromised machine. The package removal is necessary but insufficient to ensure complete remediation, as additional malicious components may persist.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

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

Technical details

References

Community reviews