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

parwo-poke63 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

parwo-poke63 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to manipulate developer reputation scores through the creation of derivative packages. The malicious nature of this package lies in its ability to automatically generate and publish numerous variants, thereby polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in parwo-poke63 originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, contributing to the inflation of developer reputation scores. The continuous republishing of these variants can lead to a cluttered npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their projects.

How To Fix

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

npm uninstall parwo-poke63

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-poke63 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring access to your code or installation.

Conclusion

The parwo-poke63 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate developer reputation scores. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for parwo-poke63 →

Share this vulnerability

FAQ

parwo-poke63 is an npm package linked to a malicious campaign that manipulates developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially introducing security risks into your project.

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

If you have installed parwo-poke63, it is advisable to remove it from your project and look for alternative packages.

Currently, there is no specific patch for parwo-poke63. The best course of action is to remove the package and monitor for any updates or advisories.

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

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