Malicious Code Injection in shilang-poke26: A Threat to npm Packages
Summary
MAL-2025-165843: Malicious code in shilang-poke26 (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-poke26 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards associated with the tea.xyz protocol. Its functionality is compromised by the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in shilang-poke26 originates from its association with a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shilang-poke26If 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, avoid using the shilang-poke26 package and monitor your package-lock.json file for any unauthorized changes. You can also use tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The shilang-poke26 package poses a significant threat due to its malicious code that manipulates package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive can help mitigate risks associated with open-source dependencies.
See every vulnerability recorded for shilang-poke26 →
FAQ
shilang-poke26 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your application.
If you have installed shilang-poke26, you should uninstall it immediately using the command npm uninstall shilang-poke26 and review your project's dependencies for any other malicious packages.
You can use Vulert to monitor your project for open-source vulnerabilities in real-time. It analyzes your package-lock.json file to alert you of any issues.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
