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

shilang-poke109 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165825: Malicious code in shilang-poke109 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

shilang-poke109 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, allowing developers to publish and manage their packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in shilang-poke109 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to the pollution of the npm registry with derivative packages. The ramifications include potential security risks for users who unknowingly install these compromised packages, as they may contain further vulnerabilities or malicious code.

How To Fix

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

npm uninstall shilang-poke109

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 the shilang-poke109 package until a secure version is released. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The shilang-poke109 package poses a significant risk to npm users due to its malicious code that alters package metadata and floods the npm registry with compromised packages. It is crucial for developers to stay informed about such vulnerabilities and utilize tools like Vulert for ongoing monitoring.

See every vulnerability recorded for shilang-poke109 →

Share this vulnerability

FAQ

shilang-poke109 is an npm package associated with the tea.xyz token reward campaign, designed to publish and manage packages in the npm registry.

The package modifies package.json files, removes private flags, and generates random package names to inflate developer reputation scores, leading to npm registry pollution.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

If you have installed shilang-poke109, it is advisable to update the package to a patched version or remove it from your project until a secure version is available.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights without requiring code access.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall shilang-poke109

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