Malicious Code Injection in carpo-hermes-firebase-nightmare Package

Summary

13/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-186006: Malicious code in carpo-hermes-firebase-nightmare (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The carpo-hermes-firebase-nightmare package is part of the npm ecosystem, typically used for integrating Firebase with Hermes in React Native applications. It is designed to facilitate seamless communication between Firebase services and React Native apps. However, this package has been identified as part of a malicious campaign that exploits npm's package management system, leading to significant security risks.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts that automatically modify the package.json file, removing private flags and altering version numbers. They generate random package names, often themed around Indonesian culture, and continuously republish these variants to pollute the npm registry. This not only compromises the integrity of the affected package but also poses risks to developers who may unknowingly use these malicious versions.

How To Fix

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

npm uninstall carpo-hermes-firebase-nightmare

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 carpo-hermes-firebase-nightmare package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time based on your package-lock.json file.

Conclusion

The carpo-hermes-firebase-nightmare package has been identified as a vector for malicious code injection due to its association with a token reward campaign. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.

See every vulnerability recorded for carpo-hermes-firebase-nightmare →

Share this vulnerability

FAQ

It is an npm package used for integrating Firebase with Hermes in React Native applications.

The vulnerability can lead to the injection of malicious code, compromising your project's security and potentially affecting your application's integrity.

You should uninstall the package immediately and look for alternatives that do not have known vulnerabilities.

You can use Vulert to monitor your project's dependencies in real-time by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall carpo-hermes-firebase-nightmare

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