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

parwo-poke68 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

parwo-poke68 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. It is designed to manipulate package metadata and publish numerous derivative packages with the intent of inflating developer reputation scores for token rewards. This package is not only harmful to individual developers but also poses a risk to the integrity of the npm registry as a whole.

Vulnerability Detail

The vulnerability in parwo-poke68 originates from its malicious design, which includes scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants that clutter the npm registry, making it difficult for legitimate packages to be found and potentially leading to security risks for users who inadvertently install these malicious packages.

How To Fix

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

npm uninstall parwo-poke68

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 measure, users can avoid using the parwo-poke68 package and monitor their package dependencies for any signs of malicious activity. Additionally, consider using tools like Vulert to monitor for vulnerabilities in your project's package-lock.json file.

Conclusion

The parwo-poke68 package poses a significant threat to npm users due to its malicious code that modifies package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security and integrity of their projects.

See every vulnerability recorded for parwo-poke68 →

Share this vulnerability

FAQ

parwo-poke68 is an npm package identified as part of a malicious campaign that modifies package metadata to inflate developer reputation scores.

The vulnerability can lead to the installation of malicious packages that clutter the npm registry and potentially compromise the security of your project.

You should remove the parwo-poke68 package from your project and monitor for any updates or patches that may address this vulnerability.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.

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

How To Fix

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

npm uninstall parwo-poke68

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