MalwarePublished 13 Jul 2026

abuden25 (npm) · Malicious Code

Affects abuden25Source GCVE Database

Malicious package : remove abuden25 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-10274

What to do

Remove abuden25 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
npmabuden25	Affected =2.0.0 =1.7.7 =1.1.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 'abuden25' contains malicious code that compromises any computer on which it is installed or running. Installation of this package may result in full system compromise, including unauthorized access to secrets and keys stored on the affected machine. Removing the package alone may not fully eliminate the malicious presence, as the attacker may have established persistent control over the system.

Impact

Full compromise of the affected system is expected. All secrets and keys stored on the compromised computer are at risk and should be rotated immediately from a secure, unaffected environment. The presence of this package indicates that an attacker may have established persistent control, leading to potential data theft, system manipulation, or further malicious activity.

Defensive guidance

Remove the 'abuden25' package immediately from affected systems. Rotate all secrets and keys that were stored on the compromised machine using a different, secure computer. Due to the likelihood of persistent compromise, consider rebuilding the affected system from a known clean state to ensure complete removal of malicious code and backdoors.

Summary

The 'abuden25' package in the npm ecosystem is identified as malicious software. According to the source details, any system with this package installed should be considered fully compromised. The attacker may have gained full control, and secrets or keys stored on the system are at risk. Removal of the package is recommended but may not suffice to fully remediate the infection due to potential persistence mechanisms.

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