Malicious Code Injection in shilang-poke1: A Threat to npm Users

shilang-poke1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165814: Malicious code in shilang-poke1 (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-poke1 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the distribution of token rewards through various scripts. However, it has been identified as containing malicious code that can compromise the integrity of the npm registry and the projects that depend on it.

Vulnerability Detail

The vulnerability in shilang-poke1 originates from its inclusion in a campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file, removing private flags and changing version numbers. The malicious payload generates random package names and continuously republishes variants, leading to pollution of the npm registry and potential security risks for developers using these packages.

How To Fix

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

npm uninstall shilang-poke1

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 avoid using shilang-poke1 and any packages that may depend on it. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The shilang-poke1 package poses a significant risk due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their projects.

See every vulnerability recorded for shilang-poke1 →

Share this vulnerability

FAQ

shilang-poke1 is an npm package involved in the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, affecting the integrity of your project.

You should remove the shilang-poke1 package from your project and monitor for any updates or patches.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies using tools like npm audit and stay informed about vulnerabilities in the packages you use.

How To Fix

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

npm uninstall shilang-poke1

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