Critical Malicious Code Vulnerability in brioche-apl-dev-env Package

brioche-apl-dev-env Updated 02 Oct 2026

Summary

30/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17432: Malicious code in brioche-apl-dev-env (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The brioche-apl-dev-env package is a dependency-confusion package designed to mimic an internal project. It uses an inflated version number (100.0.0) to outrank private registry versions. This package runs a preinstall script that collects sensitive information about the user's environment and sends it to a remote server.

Vulnerability Detail

The vulnerability arises from the malicious code embedded in the setup.js file, which is executed during the preinstall phase of the npm install process. This script collects sensitive information such as hostname, username, working directory, OS, architecture, Node.js version, and npm registry configuration, and sends it to a remote server via an HTTPS POST request. The implications of this vulnerability include unauthorized data collection and potential exposure of sensitive user information.

How To Fix

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

npm uninstall brioche-apl-dev-env

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 prevent the execution of the preinstall script by using the following command when installing packages: npm install --ignore-scripts. However, this may not be a long-term solution, and it is advisable to remove the package entirely.

Conclusion

The brioche-apl-dev-env package contains a critical vulnerability due to embedded malicious code that collects sensitive information. It is crucial to remove this package and monitor your application for potential impacts. Utilizing tools like Vulert can help in identifying such vulnerabilities in the future.

See every vulnerability recorded for brioche-apl-dev-env →

Share this vulnerability

FAQ

It is a dependency-confusion package that mimics an internal project and runs a malicious script during installation.

The vulnerability can lead to unauthorized data collection from your environment, exposing sensitive information.

You should remove the brioche-apl-dev-env package immediately and monitor your environment for any suspicious activity.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Vulert is a tool that monitors open-source vulnerabilities in your software using just the package-lock.json file, providing real-time alerts.

How To Fix

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

npm uninstall brioche-apl-dev-env

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