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

shilang-poke88 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165911: Malicious code in shilang-poke88 (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

shilang-poke88 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with a series of malicious activities aimed at inflating developer reputation scores. This package is designed to automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and potential security risks for users relying on these packages.

Vulnerability Detail

The vulnerability in shilang-poke88 arises from its malicious code that modifies the package.json file to remove private flags and alter version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only clutters the npm registry but also poses a risk of unintentional dependency on compromised packages, potentially leading to further exploitation.

How To Fix

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

npm uninstall shilang-poke88

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, users can avoid using the shilang-poke88 package until a fix is confirmed. 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-poke88 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with compromised packages. Users are advised to update or remove the package and utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for shilang-poke88 →

Share this vulnerability

FAQ

shilang-poke88 is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities in the npm ecosystem.

The vulnerability can lead to the inclusion of malicious code in your project, which may compromise security and lead to unintended consequences.

If you have installed shilang-poke88, it is recommended to update the package to a patched version or remove it entirely until a fix is available.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. It requires only the package-lock.json file.

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

How To Fix

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

npm uninstall shilang-poke88

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