Malicious Code Injection in teagood-sukuna74: A Threat to npm Users
Summary
MAL-2025-167831: Malicious code in teagood-sukuna74 (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-sukuna74 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in teagood-sukuna74 originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant issues, including the potential for developers to unknowingly use compromised packages, which can result in data breaches or further exploitation of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-sukuna74
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 teagood-sukuna74 package from your project by executing: 'npm uninstall teagood-sukuna74'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The teagood-sukuna74 package has been identified as containing malicious code that poses a significant risk to npm users. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for teagood-sukuna74 →
FAQ
The primary risk is that it can lead to the installation of compromised packages, which may expose sensitive data or allow unauthorized access to systems.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground at Vulert Scanner, you can check your application without any signup.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate the risk.
The malicious code modifies package.json files to remove private flags and generates random package names, continuously republishing them to clutter the npm registry.
Regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and ensure to only install packages from trusted sources.