Malicious Code Injection in shilang-poke31: A Threat to npm Users
Summary
MAL-2025-165849: Malicious code in shilang-poke31 (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-poke31 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. It aims to inflate developer reputation scores for rewards associated with the tea protocol. However, this functionality has been compromised, leading to significant security concerns.
Vulnerability Detail
The vulnerability in shilang-poke31 originates from its association with malicious autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, which are then continuously republished to pollute the npm registry. This behavior can lead to unauthorized access, reputation damage for developers, and a cluttered npm ecosystem, making it difficult for legitimate packages to be discovered.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shilang-poke31If 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-poke31 package from your project by executing: npm uninstall shilang-poke31. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The shilang-poke31 package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for shilang-poke31 →
FAQ
The main issue is that it contains malicious code that modifies package.json and repopulates the npm registry with harmful packages.
You can use Vulert to monitor your application for vulnerabilities. By analyzing your package-lock.json file, Vulert provides real-time alerts for any open-source vulnerabilities.
If you have installed shilang-poke31, it is recommended to uninstall the package immediately and check for any updates or patches.
Yes, tools like Vulert can help you monitor and alert for open-source vulnerabilities in your software without requiring access to the code.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
