Malicious Code Injection in quickest_woodpecker-excellentdev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107657: Malicious code in quickest_woodpecker-excellentdev (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The quickest_woodpecker-excellentdev package is part of the npm ecosystem, designed for developers to enhance their applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities. This package is involved in generating and publishing derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that floods npm with malicious packages. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package.

How To Fix

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

npm uninstall quickest_woodpecker-excellentdev

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 remove the quickest_woodpecker-excellentdev package from your project by executing the command: 'npm uninstall quickest_woodpecker-excellentdev'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The quickest_woodpecker-excellentdev package has been identified as containing malicious code that can compromise applications. It is crucial for developers to take immediate action by updating or uninstalling the package to protect their projects from potential threats.

See every vulnerability recorded for quickest_woodpecker-excellentdev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.

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

You should immediately update or uninstall the quickest_woodpecker-excellentdev package to mitigate the risk of exploitation.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall quickest_woodpecker-excellentdev

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