Malicious Code Injection in teagood-sukuna13: A Threat to npm Ecosystem
Summary
MAL-2025-167765: Malicious code in teagood-sukuna13 (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-sukuna13 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry and is intended for developers looking to enhance their reputation through token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm ecosystem.
Vulnerability Detail
The vulnerability in teagood-sukuna13 originates from its inclusion in a campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-sukuna13If 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, avoid using the teagood-sukuna13 package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Conclusion
The discovery of malicious code in the teagood-sukuna13 package highlights the importance of vigilance in the npm ecosystem. Developers must take proactive measures to secure their applications by removing affected packages and utilizing tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for teagood-sukuna13 →
FAQ
The primary risk is the injection of malicious code that modifies package.json files and floods the npm registry with compromised packages, potentially affecting other developers.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Simply upload your package-lock.json file to check for vulnerabilities.
You should uninstall the package immediately using 'npm uninstall teagood-sukuna13' and check your project for any other affected packages.
Yes, consider using other reputable npm packages that provide similar functionality without the associated risks. Always check the package's reputation and reviews.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the latest security advisories in the open-source community.
