How severe is GHSA-jxf5-7x3j-8j9m?

GHSA-jxf5-7x3j-8j9m has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jxf5-7x3j-8j9m?

GHSA-jxf5-7x3j-8j9m affects the following packages: load-from-cwd-or-npm (npm). Ecosystems affected: npm.

How do I fix GHSA-jxf5-7x3j-8j9m?

Update load-from-cwd-or-npm to 3.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jxf5-7x3j-8j9m is resolved across your whole dependency graph.

How do I detect GHSA-jxf5-7x3j-8j9m in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for load-from-cwd-or-npm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-jxf5-7x3j-8j9m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-jxf5-7x3j-8j9m actively exploited in the wild?

No public exploit code has been indexed for GHSA-jxf5-7x3j-8j9m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-jxf5-7x3j-8j9m published, and has it been updated?

GHSA-jxf5-7x3j-8j9m was published on September 3, 2020 and was last updated on September 30, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

Malicious Package in load-from-cwd-or-npmGHSA-jxf5-7x3j-8j9m

CRITICAL

GHSA-jxf5-7x3j-8j9m is a critical-severity (CVSS 9.8) vulnerability in load-from-cwd-or-npm. A fix is available for load-from-cwd-or-npm — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Sep 30, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 30, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

7other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

load-from-cwd-or-npmnpm

500downloads / week

Description

Version 3.0.2 of load-from-cwd-or-npm contains malicious code. The malware breaks functionality of the purescript-installer package by injecting targeted code.

Recommendation

Upgrade to version 3.0.4 or later. There is no indication of further compromise.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`load-from-cwd-or-npm`	≥ 3.0.2&&< 3.0.4	3.0.4`npm install load-from-cwd-or-npm@3.0.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for load-from-cwd-or-npm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update load-from-cwd-or-npm to 3.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jxf5-7x3j-8j9m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Version 3.0.2 of `load-from-cwd-or-npm` contains malicious code. The malware breaks functionality of the `purescript-installer` package by injecting targeted code. ## Recommendation Upgrade to version 3.0.4 or later. There is no indication of further compromise.

O3 Security · Impact-Aware SCA

Is GHSA-jxf5-7x3j-8j9m in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works