Malicious Code Injection in sudden_haddock_0xrequest Package

sudden_haddock_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109272: Malicious code in sudden_haddock_0xrequest (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 sudden_haddock_0xrequest package is part of the npm ecosystem, often used for various JavaScript applications. It has been identified as part of a broader campaign that exploits npm's package publishing system. This package, like many others in this campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the sudden_haddock_0xrequest package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these tainted packages, leading to potential security breaches and loss of trust in the ecosystem.

How To Fix

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

npm uninstall sudden_haddock_0xrequest

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 measure, you can avoid using the sudden_haddock_0xrequest package and any other packages that are part of the tea.xyz token reward campaign. Additionally, you can implement stricter controls on package installations and regularly audit your dependencies.

Conclusion

The sudden_haddock_0xrequest package poses a significant risk due to its malicious behavior of modifying project files and publishing derivative packages. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure the security of their applications.

See every vulnerability recorded for sudden_haddock_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

Using this package can compromise the integrity of your project and lead to security risks, as it modifies essential files and may introduce malicious code.

You should uninstall the package immediately using the command npm uninstall sudden_haddock_0xrequest.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and avoid using packages from untrusted sources.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check if your application is affected by vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall sudden_haddock_0xrequest

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