Malicious Code Injection in teagood-nakamala42: npm Package Vulnerability
Summary
MAL-2025-167307: Malicious code in teagood-nakamala42 (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
teagood-nakamala42 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been identified as containing malicious code that modifies package metadata and floods the npm registry with unwanted packages.
Vulnerability Detail
The vulnerability in teagood-nakamala42 originates from its malicious payload that alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also inflates developer reputation scores fraudulently, posing risks to developers and users relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-nakamala42
If 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 workaround, you can remove the affected package from your project by executing: 'npm uninstall teagood-nakamala42'. This will prevent any malicious code from executing in your environment until a fix is applied.
Conclusion
The teagood-nakamala42 npm package has been identified as containing malicious code that compromises the integrity of the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.
See every vulnerability recorded for teagood-nakamala42 →
FAQ
The vulnerability can lead to the proliferation of malicious packages in the npm registry, affecting the integrity of the ecosystem and potentially compromising other projects that depend on these packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected by this vulnerability without any signup.
If updating is not an option, consider removing the package from your project and replacing it with a safer alternative until a patch is available.
This vulnerability can disrupt your development process by introducing unreliable packages, which may lead to unexpected behavior in your application and increased maintenance overhead.
To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and ensure to only use packages from trusted sources.