CVE-2022-3454: Malicious code in grenache-browser-http (npm)

grenache-browser-http Updated 02 Oct 2025

Summary

20/06/2022
CRITICAL
No i
Critical
Not published

MAL-2022-3454: Malicious code in grenache-browser-http (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The grenache-browser-http package is an npm package that provides functionality for making HTTP requests in the Grenache framework. It is commonly used in Node.js applications to communicate with other services over HTTP. The package is vulnerable to a malicious code injection attack, which can compromise the security of the host system and expose sensitive information.

Vulnerability Detail

The vulnerability originates from a specific version of the grenache-browser-http package (version 0.0.0). This version contains malicious code that can fully compromise any computer on which it is installed or running. Once installed, the malicious code can give full control of the computer to an external entity, potentially leading to the theft of secrets and keys stored on that computer. Removing the package may not guarantee the removal of all malicious software resulting from its installation. The impact of this vulnerability is severe, as it can lead to unauthorized access and data breaches.

How To Fix

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

npm uninstall grenache-browser-http

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

There is no specific workaround mentioned for this vulnerability. The recommended course of action is to follow the steps outlined in the 'how_to_fix' section to mitigate the risk and ensure the security of the system.

Conclusion

The grenache-browser-http package (version 0.0.0) is vulnerable to a malicious code injection attack that can fully compromise the host system. It is crucial to take immediate action by rotating all secrets and keys stored on affected computers and removing the package. However, it is important to note that removing the package may not completely remove all malicious software. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for grenache-browser-http →

Share this vulnerability

FAQ

This vulnerability can fully compromise any computer on which the grenache-browser-http package (version 0.0.0) is installed or running. It can give unauthorized access to the computer and potentially lead to the theft of sensitive information.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the package-lock.json file.

If your system is affected by this vulnerability, it is recommended to immediately rotate all secrets and keys stored on the affected computer from a different computer. Additionally, remove the grenache-browser-http package, although it may not completely remove all malicious software.

Rotating all secrets and keys is the recommended course of action to ensure the security of the system. It is important to perform this step from a different computer to prevent potential compromise of the new secrets and keys.

There is no guarantee that removing the grenache-browser-http package will remove all malicious software that may have been installed as a result of its presence. Additional measures should be taken to ensure the security of the affected system.

How To Fix

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

npm uninstall grenache-browser-http

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