Malicious Code Injection in shilang-poke72: A Threat to npm Users
Summary
MAL-2025-165894: Malicious code in shilang-poke72 (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-poke72 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The package's functionality is compromised, making it a potential threat to users who may unknowingly install it.
Vulnerability Detail
The vulnerability in shilang-poke72 originates from its association with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses risks to developers who may inadvertently trust and use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shilang-poke72If 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 measure, avoid using shilang-poke72 and any other packages associated with the tea.xyz campaign. Regularly audit your package-lock.json file to identify and remove any malicious packages. You can also use tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The discovery of malicious code in the shilang-poke72 package highlights the importance of vigilance in the npm ecosystem. Users are advised to uninstall the affected package and utilize tools like Vulert to monitor their dependencies for potential vulnerabilities. Staying informed and proactive can help mitigate risks associated with malicious packages.
See every vulnerability recorded for shilang-poke72 →
FAQ
shilang-poke72 is an npm package identified as part of a malicious campaign that manipulates the npm registry.
The malicious code modifies your package.json, removes private flags, and generates random package names, potentially leading to security risks.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Uninstall the package immediately using 'npm uninstall shilang-poke72' and check for any other affected packages.
Yes, Vulert provides real-time monitoring for open-source vulnerabilities using your package-lock.json file.
