Malicious Code Injection in teagood-sukuna57: A Threat to npm Packages
Summary
MAL-2025-167812: Malicious code in teagood-sukuna57 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
teagood-sukuna57 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, often with randomized names, to inflate developer reputation scores for rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in teagood-sukuna57 originates from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially harm developers relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-sukuna57If 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-sukuna57 package from your project by executing the command: npm uninstall teagood-sukuna57. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The teagood-sukuna57 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to update or remove this package to maintain the integrity of their projects. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.
See every vulnerability recorded for teagood-sukuna57 →
FAQ
The primary threat is the injection of malicious code that modifies package.json files and floods the npm registry with unwanted packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By simply checking your package-lock.json file, you can determine if your application is affected.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time without requiring code access or installation.
You can find detailed information about this vulnerability in the official npm registry or by visiting the GitHub repository for malicious packages.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
