Malicious Code Injection in teagood-sukuna31: A Threat to npm Users
Summary
MAL-2025-167785: Malicious code in teagood-sukuna31 (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-sukuna31 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate token rewards for developers by automatically generating and publishing derivative packages. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with unwanted variants.
Vulnerability Detail
The vulnerability originates from the malicious design of the teagood-sukuna31 package, which includes autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may affect their applications' security and integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-sukuna31
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 avoid using the teagood-sukuna31 package and any other packages associated with the tea.xyz token reward campaign until a secure version is released. Regularly monitor your dependencies for any updates or patches.
Conclusion
The discovery of malicious code in the teagood-sukuna31 package highlights the importance of vigilance in managing npm dependencies. By understanding the nature of this vulnerability and taking proactive steps to mitigate risks, developers can better protect their applications from potential threats.
See every vulnerability recorded for teagood-sukuna31 →
FAQ
The malicious code can lead to the modification of your project's package.json, potentially introducing security vulnerabilities and affecting application stability.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without needing to sign up.
Immediately uninstall the package using 'npm uninstall teagood-sukuna31' and review your project for any other potentially compromised packages.
While specific alternatives depend on your use case, consider researching other npm packages that provide similar functionality without the associated risks.
Regularly check for updates to your dependencies and utilize tools like Vulert to receive real-time alerts for open-source vulnerabilities.