Malicious Code Injection in shilang-poke54: A Threat to npm Ecosystem
Summary
MAL-2025-165874: Malicious code in shilang-poke54 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
shilang-poke54 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 manipulate package metadata and flood the npm registry with unwanted variants.
Vulnerability Detail
The vulnerability in shilang-poke54 originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm platform.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shilang-poke54If 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, you can avoid using shilang-poke54 and any other packages associated with the tea.xyz campaign. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.
Conclusion
The discovery of malicious code in the shilang-poke54 npm package highlights the ongoing risks associated with open-source software. Developers must remain vigilant and proactive in monitoring their dependencies to safeguard their projects from potential threats. Utilizing tools like Vulert can aid in identifying vulnerabilities and maintaining the integrity of your software.
See every vulnerability recorded for shilang-poke54 →
FAQ
shilang-poke54 is an npm package linked to a malicious campaign that aims to inflate developer reputation scores through the automatic publication of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall shilang-poke54' and review your project for any other potentially compromised packages.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.
No, there are no patches available for shilang-poke54 as it is a malicious package. The best course of action is to remove it from your project.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
