Malicious Code Injection in parwo-poke51: A Threat to npm Ecosystem

parwo-poke51 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164024: Malicious code in parwo-poke51 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

parwo-poke51 is an npm package that is part of a broader campaign aimed at exploiting the npm registry. It is designed to facilitate the distribution of software packages, but it has been compromised to include malicious scripts that manipulate package metadata and publish unauthorized variants. This vulnerability poses a significant risk to developers and users relying on the integrity of npm packages.

Vulnerability Detail

The vulnerability in parwo-poke51 originates from its association with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, potentially compromising the security and reliability of other packages and affecting developers' reputations.

How To Fix

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

npm uninstall parwo-poke51

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, avoid using the parwo-poke51 package and monitor your project for any dependencies that may have been affected by this malicious code. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The parwo-poke51 package has been compromised, posing a significant risk to the npm ecosystem. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive can help mitigate the risks associated with malicious packages.

See every vulnerability recorded for parwo-poke51 →

Share this vulnerability

FAQ

parwo-poke51 is an npm package that has been identified as malicious and is part of a campaign to exploit the npm registry.

The vulnerability can lead to unauthorized modifications of your package metadata and the introduction of malicious variants, compromising your project's integrity.

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

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time, providing alerts for any issues.

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-poke51

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