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

shilang-poke82 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165905: Malicious code in shilang-poke82 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

shilang-poke82 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is linked to the tea.xyz token reward initiative, which aims to inflate developer reputation scores by flooding the registry with derivative packages. The malicious nature of this package compromises its integrity and poses significant risks to users who may unknowingly incorporate it into their projects.

Vulnerability Detail

The vulnerability in shilang-poke82 originates from its design to execute autopublish scripts that modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of variants. The ramifications include potential exposure to malicious code, pollution of the npm registry, and undermining the trust in the ecosystem. This vulnerability is particularly concerning as it can affect any project that depends on this package, leading to security breaches and loss of data integrity.

How To Fix

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

npm uninstall shilang-poke82

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 avoid using shilang-poke82 and replace it with a trusted alternative. Always validate the packages you intend to use by checking their source and reputation within the community.

Conclusion

The discovery of malicious code in the shilang-poke82 package highlights the importance of vigilance when using open-source packages. By understanding the nature of this vulnerability and taking appropriate actions, developers can protect their projects from potential threats. Regular monitoring and using tools like Vulert can further enhance security.

See every vulnerability recorded for shilang-poke82 →

Share this vulnerability

FAQ

shilang-poke82 is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.

You should immediately uninstall the package using npm uninstall shilang-poke82 and check your project for any unintended consequences.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall shilang-poke82

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