# Lightdash CLI supply chain compromise via axios malware

Source: https://junglewise.ai/threats/lightdash-lightdash-cli-supply-chain-attack-via-compromised-axios-05be2e70  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-02. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

Severity: low · CVSS 3.1 · Published 2026-04-02

Lightdash CLI, a command-line tool for analytics and business intelligence, can resolve to compromised versions of the axios HTTP library that contain a remote access trojan (RAT). An attacker compromised the axios maintainer's npm account and published malicious versions (1.14.1 and 0.30.4) containing malware for approximately 3 hours on March 31, 2026. Users of Lightdash CLI versions 0.1800.0 through 0.2695.0 who installed without a pre-existing lockfile during this window may have installed the RAT, granting attackers shell access and full machine compromise.

Technologies: [Axios](https://junglewise.ai/threats/technologies/axios). Vendors: [Axios](https://junglewise.ai/threats/vendors/axios), [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is This vulnerability exploited in the wild?** No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

**How severe is This vulnerability?** Low severity, with a CVSS score of 3.1, published 2 April 2026.

**Which products and versions are affected?** Axios 1.14.1, 0.30.4; @lightdash/cli (npm) SEMVER:introduced=0.1800.0,fixed=0.2695.1.

**Is there a fix for This vulnerability?** Yes. @lightdash/cli (npm): upgrade to 0.2695.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is This vulnerability attacked?** It is attacked over the network, in a software library.

**Am I affected?** Check whether you run Axios or @lightdash/cli (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- @lightdash/cli (npm): upgrade to 0.2695.1 or later

  ```sh
  npm install @lightdash/cli@0.2695.1
  ```


## Technical details

This is a supply chain attack exploiting npm package resolution. An attacker compromised the axios npm account and published malicious versions (1.14.1 and 0.30.4) containing an obfuscated postinstall script that pulls in a malicious transitive dependency (plain-crypto-js@4.2.1). Lightdash CLI specifies axios with a permissive semver range (^1.12.0), allowing resolution to the compromised versions. Users performing fresh installs of affected Lightdash CLI versions (0.1800.0–0.2695.0) between 2026-03-31T00:21 UTC and 03:29 UTC without a pre-existing lockfile were at risk. The injected RAT establishes persistence via platform-specific payloads (macOS: /Library/Caches/com.apple.act.mond, Windows: %PROGRAMDATA%\wt.exe, Linux: /tmp/ld.py) and connects to a command-and-control server (sfrclak.com/142.11.206.73:8000) to provide shell access, file enumeration, and arbitrary command execution. Lightdash 0.2695.1 patches the vulnerability by pinning axios to version 1.14.0.

## Affected products

- Lightdash @lightdash/cli >=0.1800.0, <0.2695.1
- axios axios 1.14.1, 0.30.4

## Timeline

- 2026-03-31: other: Malicious axios versions 1.14.1 and 0.30.4 published to npm
- 2026-03-31: exploited: Malicious versions live on npm for approximately 3 hours
- 2026-03-31: disclosed: axios GitHub issue #10604 opened reporting compromise
- 2026-03-31: other: Malicious versions removed from npm registry
- 2026-03-31: advisory: GitHub advisory GHSA-fw8c-xr5c-95f9 published for axios malware
- 2026-04-02: advisory: GHSA-3hfp-gqgh-xc5g published documenting impact on Lightdash CLI
- 2026-04-02: patched: @lightdash/cli@0.2695.1 released with axios pinned to 1.14.0

## References

- [https://github.com/lightdash/lightdash/security/advisories/GHSA-3hfp-gqgh-xc5g](https://github.com/lightdash/lightdash/security/advisories/GHSA-3hfp-gqgh-xc5g)
- [https://github.com/axios/axios/issues/10604](https://github.com/axios/axios/issues/10604)
- [https://github.com/lightdash/lightdash](https://github.com/lightdash/lightdash)
- [https://security.snyk.io/vuln/SNYK-JS-AXIOS-15850650](https://security.snyk.io/vuln/SNYK-JS-AXIOS-15850650)
- [https://security.snyk.io/vuln/SNYK-JS-PLAINCRYPTOJS-15850652](https://security.snyk.io/vuln/SNYK-JS-PLAINCRYPTOJS-15850652)
- [https://socket.dev/blog/axios-npm-package-compromised](https://socket.dev/blog/axios-npm-package-compromised)

## Related threats

- [Axios NO_PROXY CIDR notation bypass in Node.js adapter](https://junglewise.ai/threats/cve-2026-101899-axios-cidr-form-no-proxy-entries-are-ignored-causing-proxy)
- [Axios prototype pollution in ToFormData](https://junglewise.ai/threats/cve-2026-101909-axios-is-a-promise-based-http-client-for-the-browser-and-node-js)
- [Axios fetch adapter header injection via prototype pollution](https://junglewise.ai/threats/cve-2026-101908-axios-is-a-promise-based-http-client-for-the-browser-and-node-js)
- [Axios fetch adapter maxRedirects bypass](https://junglewise.ai/threats/cve-2026-101907-axios-is-a-promise-based-http-client-for-the-browser-and-node-js)
- [Axios ReDoS in shouldBypassProxy regular expression](https://junglewise.ai/threats/cve-2026-101906-axios-is-a-promise-based-http-client-for-the-browser-and-node-js)