Malicious Code Injection in quickest_haddock_z3n Package

quickest_haddock_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107652: Malicious code in quickest_haddock_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 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 quickest_haddock_z3n package is part of the npm ecosystem, often utilized for various JavaScript functionalities. However, it has been identified as a malicious package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the quickest_haddock_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

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

Conclusion

The quickest_haddock_z3n package poses significant risks due to its embedded malicious code, which can compromise your application and pollute the npm registry. It is essential to remove this package and monitor your dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for quickest_haddock_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as malicious, designed to inflate developer reputation scores through the automatic generation of derivative packages.

The malicious code modifies your package.json file and can lead to the installation of compromised packages, which may introduce security vulnerabilities in your application.

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

You should uninstall the quickest_haddock_z3n package immediately and look for alternatives. Use the command 'npm uninstall quickest_haddock_z3n' to remove it.

While specific alternatives depend on your use case, consider searching the npm registry for similar packages that do not have a history of malicious activity.

How To Fix

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

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