Malicious Code Injection in parwo-poke78: npm Package Vulnerability

parwo-poke78 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164053: Malicious code in parwo-poke78 (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 npm package 'parwo-poke78' is part of a larger ecosystem that has been exploited for malicious purposes. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that contain harmful scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'parwo-poke78' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the security of the affected package but also affects the overall trustworthiness of the npm ecosystem, potentially leading to the installation of harmful software by unsuspecting developers.

How To Fix

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

npm uninstall parwo-poke78

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 'parwo-poke78' and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'parwo-poke78' npm package is a clear example of how malicious actors can exploit open-source ecosystems. By understanding the nature of this vulnerability and taking proactive steps to mitigate risks, developers can protect their applications and maintain the integrity of their software supply chain.

See every vulnerability recorded for parwo-poke78 →

Share this vulnerability

FAQ

'parwo-poke78' is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The vulnerability can lead to the installation of malicious code, compromising the security of your application and potentially affecting other dependencies.

You should remove 'parwo-poke78' from your project and monitor for any updates or patches that may address this vulnerability.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time, ensuring you are alerted to any issues.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

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

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