Malicious Code Injection in shilang-poke36: A Threat to npm Users
Summary
MAL-2025-165854: Malicious code in shilang-poke36 (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-poke36 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 through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in shilang-poke36 originates from its design to include autopublish scripts that manipulate the package.json file. This manipulation removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly install these malicious packages, as they may inadvertently expose their applications to further vulnerabilities or malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shilang-poke36If 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-poke36 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The shilang-poke36 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and republish variants. Developers are urged to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.
See every vulnerability recorded for shilang-poke36 →
FAQ
shilang-poke36 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of malicious packages that compromise the security of your application, potentially exposing it to further attacks.
You should immediately remove the shilang-poke36 package from your project and check for any other affected packages in your dependencies.
You can use tools like npm audit to check for vulnerabilities in your project dependencies. Additionally, Vulert can monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup or installation.
