Malicious Code Injection in financial_heron_0xrequest Package

financial_heron_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102721: Malicious code in financial_heron_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 financial_heron_0xrequest package is part of the npm ecosystem, typically used in financial applications. It is designed to facilitate requests related to financial transactions. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts aimed at inflating developer reputation scores through deceptive practices.

Vulnerability Detail

The vulnerability stems from malicious code embedded in the financial_heron_0xrequest 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 behavior not only pollutes the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of sensitive information.

How To Fix

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

npm uninstall financial_heron_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 workaround, you can avoid using the financial_heron_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The financial_heron_0xrequest package has been identified as containing malicious code that compromises the integrity of the npm registry and poses significant risks to developers. It is crucial to remove this package from your projects and monitor for any future vulnerabilities using tools like Vulert.

See every vulnerability recorded for financial_heron_0xrequest →

Share this vulnerability

FAQ

It is an npm package used for handling financial requests, but it has been compromised with malicious code.

You can use Vulert to analyze your package-lock.json file for vulnerabilities related to the financial_heron_0xrequest package.

You should uninstall the financial_heron_0xrequest package immediately and look for alternatives.

Yes, using this package can lead to security breaches, data loss, and exposure to malicious activities.

Regularly monitor your dependencies using tools like Vulert and stay updated on security advisories for the packages you use.

How To Fix

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

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