Malicious Code Injection in parwo-poke94: A Threat to npm Users

parwo-poke94 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

parwo-poke94 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the campaign, is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for the tea protocol token rewards, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in parwo-poke94 originates from its malicious design, which includes scripts that modify the package.json file to remove private flags and change version numbers. This allows the package to continuously republish variants with random names, polluting the npm registry. The ramifications include potential security risks for developers who inadvertently use these packages, as they may introduce unwanted code into their projects.

How To Fix

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

npm uninstall parwo-poke94

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 the parwo-poke94 package and monitor your project for any dependencies that may have inadvertently included it. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file.

Conclusion

The parwo-poke94 package poses a significant threat to npm users due to its malicious code injection capabilities. By understanding the nature of this vulnerability and taking proactive steps to remove the package and monitor your dependencies, you can safeguard your projects from potential risks.

See every vulnerability recorded for parwo-poke94 →

Share this vulnerability

FAQ

parwo-poke94 is an npm package identified as part of a malicious campaign that manipulates the npm registry.

The vulnerability can introduce malicious code into your project, potentially compromising security and functionality.

You should uninstall the package immediately using 'npm uninstall parwo-poke94' and review your project for any other affected dependencies.

Regularly update your dependencies, use trusted packages, and utilize tools like Vulert to monitor for vulnerabilities.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.

How To Fix

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

npm uninstall parwo-poke94

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