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

shilang-poke38 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165856: Malicious code in shilang-poke38 (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-poke38 is an npm package that is part of the tea.xyz token reward campaign. This package, like others in the campaign, is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. It is primarily used in the JavaScript ecosystem for various applications but has been compromised to include malicious scripts.

Vulnerability Detail

The vulnerability in shilang-poke38 originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall shilang-poke38

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-poke38 and any other packages that are part of the tea.xyz token reward campaign. Additionally, consider using a tool like Vulert to monitor your package-lock.json 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-poke38 package poses a significant risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to safeguard their applications against future vulnerabilities.

See every vulnerability recorded for shilang-poke38 →

Share this vulnerability

FAQ

shilang-poke38 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores by flooding the npm registry with compromised packages.

The vulnerability can lead to the installation of malicious code that modifies your package.json file and can potentially compromise your application's security.

You should uninstall shilang-poke38 immediately using the command 'npm uninstall shilang-poke38' and monitor your project for any other affected packages.

Using tools like Vulert can help monitor your dependencies for vulnerabilities in real-time, allowing you to take action before they affect your application.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without requiring any signup.

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-poke38

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