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

parwo-poke52 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

parwo-poke52 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards associated with the tea protocol. The malicious nature of this package poses significant risks to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in parwo-poke52 stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also exposes users to potential security risks and unreliable package versions.

How To Fix

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

npm uninstall parwo-poke52

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 workaround, you can monitor your package dependencies using tools like Vulert. By utilizing Vulert's playground at https://vulert.com/scanner, you can check if your application is affected by this vulnerability without requiring any signup. This allows you to stay informed about potential vulnerabilities in your open-source packages.

Conclusion

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

See every vulnerability recorded for parwo-poke52 →

Share this vulnerability

FAQ

parwo-poke52 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm ecosystem.

The vulnerability can compromise the integrity of your project by introducing unreliable package versions and potential security risks.

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

You can use Vulert to monitor your package dependencies in real-time for open-source vulnerabilities without needing to access the code or installation.

Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by vulnerabilities without requiring any signup.

How To Fix

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

npm uninstall parwo-poke52

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