Malicious Code Injection in front_hedgehog_z3n Package

front_hedgehog_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98726: Malicious code in front_hedgehog_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 front_hedgehog_z3n package is an npm module that has been implicated in a malicious campaign aimed at manipulating the npm registry. This package is part of a broader initiative that seeks to exploit developer reputation systems by flooding the registry with derivative packages. The malicious nature of this package lies in its ability to modify its own metadata and continuously republish itself under various names, thereby compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the front_hedgehog_z3n package. This code is designed to alter the package.json file by removing private flags and changing version numbers. It also generates random package names, often themed around Indonesian culture, and republishes these variants to clutter the npm registry. This behavior not only affects the reputation of legitimate developers but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages.

How To Fix

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

npm uninstall front_hedgehog_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 measure, avoid using the front_hedgehog_z3n package and consider replacing it with a reputable alternative. Regularly audit your package-lock.json file to identify any potentially compromised packages.

Conclusion

The front_hedgehog_z3n package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to remove this package from their projects and to utilize tools like Vulert for ongoing monitoring of vulnerabilities. Staying informed and proactive is essential to maintaining the security of your applications.

See every vulnerability recorded for front_hedgehog_z3n →

Share this vulnerability

FAQ

front_hedgehog_z3n is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The malicious code can alter your package.json file, remove private flags, and republish variants, potentially leading to dependency confusion and security risks.

You should uninstall the front_hedgehog_z3n package immediately and audit your dependencies for any other malicious packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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