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

parwo-poke45 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164017: Malicious code in parwo-poke45 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

parwo-poke45 is an npm package that is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to inflate developer reputation scores through automated scripts that generate and publish derivative packages with randomized names. The presence of such malicious code poses a significant risk to developers and users relying on the integrity of npm packages.

Vulnerability Detail

The vulnerability in parwo-poke45 originates from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The malicious payload can affect the reputation of developers and the overall trust in the npm ecosystem.

How To Fix

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

npm uninstall parwo-poke45

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 avoid using the parwo-poke45 package altogether. If it is already included in your project, remove it by running: npm uninstall parwo-poke45. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The parwo-poke45 package poses a significant risk due to its malicious code aimed at manipulating the npm ecosystem. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for parwo-poke45 →

Share this vulnerability

FAQ

parwo-poke45 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You should uninstall the package immediately using the command: npm uninstall parwo-poke45.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall parwo-poke45

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