Malicious Code Injection in shilang-poke55: A Threat to npm Ecosystem

shilang-poke55 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165875: Malicious code in shilang-poke55 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

shilang-poke55 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through various npm packages. However, it has been identified as containing malicious scripts that manipulate package metadata and flood the npm registry with derivative packages, potentially harming developers' reputations and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in shilang-poke55 stems from its inclusion in a campaign that deploys malicious code to automatically generate and publish numerous derivative packages. This code modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to the pollution of the npm registry. The origin of this issue is linked to the tea.xyz token reward scheme, which incentivizes the creation of such malicious packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall shilang-poke55

If 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-poke55 package from your project by executing the following command: npm uninstall shilang-poke55. This will prevent any malicious scripts from executing until a fix is applied.

Conclusion

The shilang-poke55 package poses a significant 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 uninstalling the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for shilang-poke55 →

Share this vulnerability

FAQ

shilang-poke55 is an npm package involved in the tea.xyz token reward campaign, which has been found to contain malicious code.

The malicious code modifies your package.json file and floods the npm registry with derivative packages, potentially harming your project's reputation.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall shilang-poke55

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback