Malicious Code Injection in daily_gibbon-excellentdev Package

daily_gibbon-excellentdev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101185: Malicious code in daily_gibbon-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 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

The daily_gibbon-excellentdev package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages. This package is particularly vulnerable due to its inclusion in a broader set of malicious packages that exploit npm's publishing mechanisms.

Vulnerability Detail

The vulnerability stems from the package being associated with a token reward campaign that floods npm with malicious packages. These packages contain scripts that automatically modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior leads to pollution of the npm registry and can compromise the integrity of applications relying on these packages. The malicious payload is designed to continuously republish variants, making it difficult to track and mitigate the issue.

How To Fix

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

npm uninstall daily_gibbon-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 avoid using the daily_gibbon-excellentdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The daily_gibbon-excellentdev package has been identified as a malicious package that poses significant risks to applications using it. It is crucial to uninstall this package and monitor for any unauthorized changes in your project. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.

See every vulnerability recorded for daily_gibbon-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 the creation of numerous derivative packages.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security.

You should uninstall the daily_gibbon-excellentdev package immediately and check for any dependencies that may rely on it.

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