Malicious Code Injection in shilang-poke48: A Threat to npm Ecosystem

shilang-poke48 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165867: Malicious code in shilang-poke48 (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-poke48 is an npm package that is part of a broader campaign targeting developers through token rewards. This package is designed to facilitate certain functionalities within the npm ecosystem, but it has been compromised, leading to significant security concerns. The malicious nature of this package stems from its involvement in generating and publishing derivative packages, which can mislead developers and inflate reputation scores fraudulently.

Vulnerability Detail

The vulnerability in shilang-poke48 originates from its association with the tea.xyz token reward campaign, which has been identified as a source of malicious packages on npm. The package contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to 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-poke48

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-poke48 package from your project by executing: npm uninstall shilang-poke48. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The shilang-poke48 package poses a significant security risk due to its malicious code that modifies package metadata and repopulates the npm registry with compromised packages. Developers are urged to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for shilang-poke48 →

Share this vulnerability

FAQ

shilang-poke48 is an npm package that has been compromised and is part of a malicious campaign targeting developers through token rewards.

The vulnerability can lead to the injection of malicious code, which may compromise your application's security and integrity.

You should immediately uninstall the package and check for any updates or patches that may address the vulnerability.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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

How To Fix

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

npm uninstall shilang-poke48

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