Malicious Code Injection in shilang-poke11: A Threat to npm Ecosystem
Summary
MAL-2025-165826: Malicious code in shilang-poke11 (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-poke11 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores by flooding the registry with derivative packages. The malicious nature of this package compromises its integrity and poses a risk to developers and users relying on it.
Vulnerability Detail
The vulnerability in shilang-poke11 stems from its inclusion in a campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and create random package names, leading to pollution of the npm registry. This not only affects the reputation of legitimate developers but also exposes users to potential security risks from unverified packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shilang-poke11If 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 measure, you can avoid using shilang-poke11 and any packages that may depend on it. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The shilang-poke11 package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers are advised to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for shilang-poke11 →
FAQ
shilang-poke11 is an npm package involved in a malicious campaign that floods the npm registry with derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially exposing your project to unverified and malicious packages.
You should remove the package from your project immediately and check for any dependencies that may rely on it.
Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
