Malicious Code Injection in absolute_woodpecker_dumbs Package

absolute_woodpecker_dumbs Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99045: Malicious code in absolute_woodpecker_dumbs (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 absolute_woodpecker_dumbs package is part of the npm ecosystem, which is widely used for JavaScript package management. This package appears to be associated with a token reward campaign that has led to the proliferation of malicious packages on npm. Its primary function is to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, this functionality has been compromised, making it susceptible to exploitation.

Vulnerability Detail

The vulnerability in the absolute_woodpecker_dumbs package stems from its malicious payload, which modifies the package.json file to remove private flags and alters 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 poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall absolute_woodpecker_dumbs

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 the absolute_woodpecker_dumbs package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.

Conclusion

The absolute_woodpecker_dumbs package presents a significant security risk due to its malicious behavior, which can compromise the integrity of applications using it. It is crucial for developers to be vigilant, remove any affected packages, and utilize monitoring tools like Vulert to safeguard their projects against such vulnerabilities.

See every vulnerability recorded for absolute_woodpecker_dumbs →

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 the automatic generation 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 absolute_woodpecker_dumbs package immediately and monitor your application for any unusual behavior.

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

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest versions to mitigate risks.

How To Fix

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

npm uninstall absolute_woodpecker_dumbs

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