Skip to content

Pin axios in bruno-electron due to compromised axios npm release #7634

@timmkrause

Description

@timmkrause

AI-generated notice: this issue was analyzed by AI and created by AI.

Hi Bruno team,

I wanted to report a supply-chain risk in packages/bruno-electron/package.json:

  • aws4-axios: ^3.3.0
  • axios: ^1.8.3
  • axios-ntlm: ^1.4.2

Background:

The concern is that fresh source installs during the compromise window could resolve the malicious axios@1.14.1 release:

  • direct via axios: ^1.8.3
  • transitively via axios-ntlm: ^1.4.2 -> axios: ^1.6.1

From what I could verify, Bruno's published GitHub releases do not appear to have been built during the compromise window, so this looks more like a source-build / CI install exposure than a confirmed release-artifact compromise.

Suggested actions:

  • pin axios to a known-safe version
  • add an override/resolution to prevent bad transitive resolution
  • refresh the lockfile
  • publish a short clarification for users about whether any official Bruno builds were produced during the affected timeframe

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions