Malicious Code Injection in shilang-poke68: A Threat to npm Ecosystem
Summary
MAL-2025-165889: Malicious code in shilang-poke68 (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-poke68 is an npm package that appears to be part of a broader malicious campaign targeting the npm registry. This package is designed to manipulate its own metadata and publish numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, specifically for the tea.xyz protocol. The vulnerability arises from the package's inherent design, which allows it to execute harmful scripts that can compromise the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in shilang-poke68 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages. These scripts modify the package.json file to remove private flags, change version numbers, and create random package names, leading to pollution of the npm registry. The malicious payload can significantly impact developers by inflating reputation scores fraudulently and potentially introducing security risks through unverified packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shilang-poke68If 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 prevent the installation of shilang-poke68 by using npm's package-lock.json file to monitor dependencies. Ensure that your package-lock.json does not include shilang-poke68 or any of its derivatives. You can also utilize tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The shilang-poke68 package poses a significant threat to the npm ecosystem due to its malicious nature and the potential for widespread impact on developers. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for shilang-poke68 →
FAQ
shilang-poke68 is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the introduction of unverified packages into your project, potentially compromising its security and integrity.
You should uninstall shilang-poke68 immediately using 'npm uninstall shilang-poke68' and review your project's dependencies for any other malicious packages.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
There are no patches available for shilang-poke68 as it is a malicious package. The best course of action is to remove it from your project.
