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

shilang-poke28 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165845: Malicious code in shilang-poke28 (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-poke28 is an npm package that has been implicated in a malicious campaign associated with the tea.xyz token reward system. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. The malicious nature of this package poses a significant risk to the integrity of the npm registry and its users.

Vulnerability Detail

The vulnerability in shilang-poke28 stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on these packages. The origin of this issue is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall shilang-poke28

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 workaround, you can manually remove the shilang-poke28 package from your project by running the command: npm uninstall shilang-poke28. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The shilang-poke28 package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for shilang-poke28 →

Share this vulnerability

FAQ

shilang-poke28 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the shilang-poke28 package immediately and monitor your project for any other vulnerable dependencies.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

How To Fix

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

npm uninstall shilang-poke28

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