Malicious Code Injection in parwo-poke86 Package

parwo-poke86 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164062: Malicious code in parwo-poke86 (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

The parwo-poke86 package is part of the npm ecosystem, which is widely used for JavaScript development. It is designed to facilitate various functionalities within applications. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This vulnerability exposes developers to risks associated with malicious code execution and registry pollution.

Vulnerability Detail

The vulnerability in the parwo-poke86 package originates from its involvement in the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that include scripts designed to modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, ultimately leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for applications using this package, as well as damage to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall parwo-poke86

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 temporarily avoid using the parwo-poke86 package and look for alternative packages that provide similar functionality without the associated risks. Always ensure to audit your dependencies regularly.

Conclusion

The parwo-poke86 package has been identified as a malicious package that poses significant risks to developers and their applications. It is essential to take immediate action to remove this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for parwo-poke86 →

Share this vulnerability

FAQ

The parwo-poke86 package is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.

This vulnerability can lead to the execution of malicious code, compromising the security of your application and polluting the npm registry.

You should uninstall the parwo-poke86 package immediately and check your project for any other potentially compromised packages.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall parwo-poke86

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