Malicious Code Injection in parwo-poke91 Package - npm Vulnerability

parwo-poke91 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164068: Malicious code in parwo-poke91 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The parwo-poke91 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the distribution of JavaScript packages, but it has been compromised to include malicious scripts that manipulate package metadata. This vulnerability allows attackers to exploit the npm registry, potentially affecting developers and users relying on this package.

Vulnerability Detail

The vulnerability originates from the parwo-poke91 package, which contains malicious code that modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes these variants, polluting the npm registry. This can lead to reputation inflation for malicious actors and may compromise 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-poke91

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-poke91 package and replace it with a similar package that does not have known vulnerabilities. Always verify the integrity of packages before installation.

Conclusion

The parwo-poke91 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.

See every vulnerability recorded for parwo-poke91 →

Share this vulnerability

FAQ

The parwo-poke91 package is an npm package that has been compromised to include malicious code aimed at manipulating package metadata and inflating developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help you identify if your application is affected by this vulnerability.

The risks include potential exploitation of the npm registry, reputation damage for developers, and the introduction of malicious packages into your project, which can lead to security breaches.

There is no direct patch for the parwo-poke91 package due to its malicious nature. The recommended action is to uninstall the package and avoid using it.

You can use tools like Vulert, which allows you to check your application for vulnerabilities in real-time without requiring code access or installation. Visit the Vulert playground to analyze your package-lock.json.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall parwo-poke91

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