Malicious Code Injection in tasty_duck-excellentdev Package

tasty_duck-excellentdev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109513: Malicious code in tasty_duck-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The tasty_duck-excellentdev package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, exposing their applications to potential security threats.

How To Fix

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

npm uninstall tasty_duck-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 tasty_duck-excellentdev package and replace it with a trusted alternative that serves the same purpose. Always verify the integrity and reputation of packages before integrating them into your project.

Conclusion

The tasty_duck-excellentdev package poses a significant security risk due to its malicious code designed to manipulate npm registry and developer reputation. It is crucial to remove this package from your projects and adopt best practices for dependency management to safeguard your applications.

See every vulnerability recorded for tasty_duck-excellentdev →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json and repackages it, leading to potential security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.

Uninstall the tasty_duck-excellentdev package immediately using 'npm uninstall tasty_duck-excellentdev' and replace it with a trusted alternative.

Yes, the malicious behavior of the package can lead to performance issues and security vulnerabilities in your application.

Regularly audit your dependencies, use trusted sources, and consider using tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall tasty_duck-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