Malicious Code Injection in shilang-poke8: A Threat to npm Users
Summary
MAL-2025-165902: Malicious code in shilang-poke8 (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
shilang-poke8 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 token rewards. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability in shilang-poke8 originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload 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, polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shilang-poke8If 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 shilang-poke8 package from your project by executing the command: 'npm uninstall shilang-poke8'. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The shilang-poke8 package is compromised by malicious code that can significantly impact npm users. It is crucial to monitor for vulnerabilities and apply updates promptly to maintain the integrity of your projects. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.
See every vulnerability recorded for shilang-poke8 →
FAQ
The malicious code modifies the package.json file to remove private flags and changes version numbers, allowing for the creation of numerous derivative packages.
This vulnerability can lead to the pollution of the npm registry, potentially affecting other packages and compromising the integrity of your project.
Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Absolutely! You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you cannot update the package right away, consider removing it from your project as a temporary measure to mitigate the risk.
