Malicious Code Injection in parwo-poke55: npm Package Vulnerability

parwo-poke55 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The npm package 'parwo-poke55' is part of a series of packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of this package is compromised due to the presence of malicious code that alters package metadata and floods the npm registry.

Vulnerability Detail

The vulnerability in 'parwo-poke55' originates from its malicious payload, which modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is intended to pollute the npm registry and can lead to significant security risks, including the potential for dependency confusion and the introduction of untrusted code into applications that rely on this package.

How To Fix

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

npm uninstall parwo-poke55

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, you can avoid using 'parwo-poke55' and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json is monitored for any unauthorized changes.

Conclusion

The 'parwo-poke55' npm package contains a serious vulnerability due to malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and monitor for any unauthorized changes. Utilizing tools like Vulert can help keep your dependencies secure.

See every vulnerability recorded for parwo-poke55 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that alters package metadata and floods the npm registry with derivative packages.

You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Using this package can lead to dependency confusion, introduction of untrusted code, and potential security breaches in your application.

Currently, there is no patched version available. It is advised to uninstall the package until a safe version is released.

Uninstall the package immediately using 'npm uninstall parwo-poke55' and monitor your project for any unauthorized changes.

How To Fix

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

npm uninstall parwo-poke55

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