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

shilang-poke15 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165831: Malicious code in shilang-poke15 (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-poke15 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The package's functionality is compromised due to the presence of malicious scripts that alter its configuration and behavior.

Vulnerability Detail

The vulnerability in shilang-poke15 originates from malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random Indonesian-themed package names and continuously republishes variants, polluting the npm registry. This can lead to security risks, including unauthorized access to sensitive data and the potential for further exploitation of affected systems.

How To Fix

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

npm uninstall shilang-poke15

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

Conclusion

The shilang-poke15 package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry with harmful variants. Users are urged to update or remove the package to safeguard their applications. Utilizing tools like Vulert can enhance security by providing real-time vulnerability alerts.

See every vulnerability recorded for shilang-poke15 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that alters package configurations and publishes harmful variants to the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Using the compromised package can lead to unauthorized access to sensitive data, reputation damage, and further exploitation of your systems.

Regularly updating your dependencies, using tools like Vulert for monitoring, and conducting security audits can help prevent similar vulnerabilities.

If immediate updates are not possible, consider uninstalling the package and monitoring your application for any suspicious activity.

How To Fix

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

npm uninstall shilang-poke15

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