Malicious Code Detected in cupduck Package - MAL-2025-17826

cupduck Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17826: Malicious code in cupduck (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The cupduck package is an npm library designed for various functionalities within JavaScript applications. It is utilized for its ease of integration and lightweight nature, making it a popular choice among developers. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the cupduck package stems from the inclusion of malicious code that can compromise the security of applications using it. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall cupduck

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, consider removing the cupduck package from your project until a secure version is released. You can do this by executing the command: npm uninstall cupduck. This will help prevent any potential exploitation of the malicious code while you await a fix.

Conclusion

The discovery of malicious code in the cupduck package highlights the importance of vigilance in managing open-source dependencies. Users must take proactive steps to update or remove affected packages to safeguard their applications from potential threats.

See every vulnerability recorded for cupduck →

Share this vulnerability

FAQ

The cupduck package is an npm library used in JavaScript applications for various functionalities, but it has recently been found to contain malicious code.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without any signup.

The malicious code can lead to unauthorized access, data breaches, and other harmful actions within your application, potentially compromising sensitive data.

As of now, there is no specific patched version available. Users are advised to monitor the package repository for updates and apply them as soon as they are released.

If immediate removal is not possible, ensure to implement additional security measures in your application to mitigate risks until the vulnerability is addressed.

How To Fix

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

npm uninstall cupduck

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