Malicious Code Injection in nudela-aaf-gaafodfa: A Threat to npm Ecosystem
Summary
MAL-2025-163702: Malicious code in nudela-aaf-gaafodfa (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The package 'nudela-aaf-gaafodfa' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious code.
Vulnerability Detail
The vulnerability in 'nudela-aaf-gaafodfa' originates from its design to include autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, thereby continuously republishing variants to pollute the npm registry. This can lead to security risks, as malicious code can be introduced into projects that depend on these packages, potentially compromising sensitive data and application integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nudela-aaf-gaafodfaIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary measure, avoid using the 'nudela-aaf-gaafodfa' package and consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your package dependencies using tools like Vulert, which analyzes your package-lock.json file for vulnerabilities.
Conclusion
The 'nudela-aaf-gaafodfa' package presents a significant security threat due to its malicious code injection capabilities. It is crucial for developers to be vigilant, remove affected packages, and employ tools like Vulert to monitor their applications for vulnerabilities. By following best practices, developers can safeguard their projects against similar risks.
See every vulnerability recorded for nudela-aaf-gaafodfa →
FAQ
The main risk is the potential introduction of malicious code into your application, which can compromise security and lead to data breaches.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using 'npm uninstall nudela-aaf-gaafodfa' and review your project's dependencies for any other potentially malicious packages.
Yes, tools like Vulert can monitor your package-lock.json file in real-time for open-source vulnerabilities, alerting you to any issues.
Always use trusted packages, regularly update your dependencies, and utilize security monitoring tools to stay informed about vulnerabilities.
