Skip to content

Axios npm Supply Chain Incident Impacting @usebruno/cli

Critical severity GitHub Reviewed Published Mar 31, 2026 in usebruno/bruno • Updated Apr 2, 2026

Package

npm @usebruno/cli (npm)

Affected versions

< 3.2.0

Patched versions

3.2.1

Description

Impact

This is a supply chain attack involving compromised versions of the axios npm package, which introduced a hidden dependency deploying a cross-platform Remote Access Trojan (RAT).

Users of @usebruno/cli who ran npm install between 00:21 UTC and ~03:30 UTC on March 31, 2026 may have been impacted.

Potential impact includes:

  • Execution of a malicious postinstall script
  • Remote Access Trojan (RAT) installation
  • Exfiltration of credentials and sensitive data

Not impacted:

  • Bruno desktop app users
  • Users who installed outside the attack window

Patches

The compromised axios versions (1.14.1, 0.30.4) have been removed from npm, and new installations will now resolve to safe versions.

Additionally, Bruno has taken further hardening steps:

  • Pinned axios to a known safe version to prevent accidental resolution to malicious releases
  • Fix implemented in: usebruno/bruno#7632

Recommendation

If users installed @usebruno/cli during the affected window:

  1. Reinstall dependencies
  2. Rotate all credentials and secrets:

For additional guidance on securing your system, refer to this article:
https://www.aikido.dev/blog/axios-npm-compromised-maintainer-hijacked-rat

References

@sreelakshmi-bruno sreelakshmi-bruno published to usebruno/bruno Mar 31, 2026
Published to the GitHub Advisory Database Apr 2, 2026
Reviewed Apr 2, 2026
Last updated Apr 2, 2026

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

Weaknesses

Download of Code Without Integrity Check

The product downloads source code or an executable from a remote location and executes the code without sufficiently verifying the origin and integrity of the code. Learn more on MITRE.

Embedded Malicious Code

The product contains code that appears to be malicious in nature. Learn more on MITRE.

Dependency on Vulnerable Third-Party Component

The product has a dependency on a third-party component that contains one or more known vulnerabilities. Learn more on MITRE.

CVE ID

CVE-2026-34841

GHSA ID

GHSA-658g-p7jg-wx5g

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.
⚡