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

shilang-poke33 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165851: Malicious code in shilang-poke33 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

shilang-poke33 is an npm package that has been identified as part of a larger campaign to exploit the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with malicious packages. The primary functionality of shilang-poke33 is to act as a token reward mechanism, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in shilang-poke33 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and create random package names, thereby polluting the npm registry. The ramifications of this vulnerability include potential reputational damage to developers, increased risk of dependency confusion, and the proliferation of malicious packages that can compromise other projects.

How To Fix

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

npm uninstall shilang-poke33

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-poke33 package from your project by executing the following command: npm uninstall shilang-poke33. This will prevent any malicious code from executing while you assess alternative solutions.

Conclusion

The shilang-poke33 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to take immediate action by removing the package and monitoring their projects for any signs of compromise. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for shilang-poke33 →

Share this vulnerability

FAQ

shilang-poke33 is an npm package that has been linked to a malicious campaign aimed at exploiting the npm registry.

The vulnerability can lead to the injection of malicious code, potentially compromising your project and affecting its integrity.

You should uninstall the package immediately and monitor your project for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay informed about the packages you include in your projects.

How To Fix

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

npm uninstall shilang-poke33

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