Malicious Code Injection in haniibaguette: A Threat to npm Ecosystem

haniibaguette Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171291: Malicious code in haniibaguette (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 haniibaguette package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can harm developers' reputations and the integrity of the registry itself.

Vulnerability Detail

The vulnerability in haniibaguette originates from its association with a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores through the automatic publication of numerous derivative packages. The ramifications include potential pollution of the npm registry, loss of trust in the ecosystem, and possible exploitation of developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall haniibaguette

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 haniibaguette package and any packages that may have been published as derivatives. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.

Conclusion

The haniibaguette package poses a significant risk to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores through the publication of derivative packages. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.

See every vulnerability recorded for haniibaguette →

Share this vulnerability

FAQ

Haniibaguette is an npm package that has been identified as part of a malicious campaign aimed at flooding the npm registry with derivative packages.

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

Using compromised packages can lead to security vulnerabilities, loss of data integrity, and potential exploitation of your application by malicious actors.

Regularly update your dependencies, monitor your package-lock.json for changes, and utilize tools like Vulert to stay informed about vulnerabilities.

There is no patch available for haniibaguette as it is recommended to uninstall the package entirely to mitigate the risk.

How To Fix

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

npm uninstall haniibaguette

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