Malicious Code Injection in shilang-poke70: A Threat to npm Ecosystem
Summary
MAL-2025-165892: Malicious code in shilang-poke70 (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-poke70 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 has been known to flood the npm ecosystem with harmful packages. The primary functionality of shilang-poke70 is to act as a derivative package that can be published and republished with altered metadata, potentially affecting developers' reputations and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in shilang-poke70 stems from its malicious code designed to manipulate package.json files. This code removes private flags, alters version numbers, and generates random package names, leading to the automatic publication of numerous derivative packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages to inflate developer reputation scores. The ramifications include pollution of the npm registry, potential security risks for applications relying on these packages, and degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shilang-poke70If 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 shilang-poke70 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to ensure no malicious packages are included.
Conclusion
The shilang-poke70 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and publish derivative packages. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove any affected packages to safeguard applications.
See every vulnerability recorded for shilang-poke70 →
FAQ
shilang-poke70 is an npm package identified as part of a malicious campaign that alters package metadata and floods the npm registry with derivative packages.
This vulnerability can lead to the pollution of the npm registry, potentially introducing security risks and affecting the integrity of your application.
You should uninstall the package immediately using npm uninstall shilang-poke70 and audit your dependencies for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
