Malicious Code Injection in teagood-sukuna22: A Threat to npm Users
Summary
MAL-2025-167775: Malicious code in teagood-sukuna22 (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-sukuna22 is a package within the npm ecosystem, part of a broader campaign associated with the tea.xyz token reward initiative. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been identified as containing malicious scripts that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in teagood-sukuna22 stems from its inclusion of malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores through the automatic publication of numerous derivative packages, ultimately polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with various malicious npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-sukuna22If 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, consider removing the teagood-sukuna22 package from your project until a secure version is released. You can do this by executing: npm uninstall teagood-sukuna22.
Conclusion
The teagood-sukuna22 package poses a significant threat due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects.
See every vulnerability recorded for teagood-sukuna22 →
FAQ
The primary risk is the potential for malicious code to compromise your project's integrity by modifying package configurations and flooding the npm registry with unwanted packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application against this vulnerability using the Vulert playground at Vulert Scanner without any signup.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risk.
As of now, it is essential to check the npm registry for any patched versions of teagood-sukuna22 that address this vulnerability.
Using compromised packages can lead to security breaches, data loss, and damage to your project's reputation, making it critical to regularly audit and update dependencies.
