Malicious Code Injection in intact_duck_z3n Package - npm Vulnerability

intact_duck_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104271: Malicious code in intact_duck_z3n (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 intact_duck_z3n package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been associated with the tea.xyz token reward campaign, which has led to the proliferation of malicious packages designed to inflate developer reputation scores. The package's functionality has been compromised, making it a vector for malicious activities.

Vulnerability Detail

The vulnerability in the intact_duck_z3n package originates from its association with a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which pollutes the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, leading to reputational damage and possible exploitation of their applications.

How To Fix

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

npm uninstall intact_duck_z3n

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 workaround, you can avoid using the intact_duck_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The intact_duck_z3n package poses a significant security risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying vigilant and informed is essential to maintaining the security of your applications.

See every vulnerability recorded for intact_duck_z3n →

Share this vulnerability

FAQ

The intact_duck_z3n package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the publication of compromised packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help you identify if your application is affected by this vulnerability.

Using the intact_duck_z3n package can lead to security vulnerabilities in your application, including potential exploitation and reputational damage due to the pollution of the npm registry.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the npm ecosystem.

If you have already used the intact_duck_z3n package, it is crucial to uninstall it immediately and replace it with a secure alternative. Additionally, review your project's dependencies for any other potential vulnerabilities.

How To Fix

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

npm uninstall intact_duck_z3n

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