How severe is GHSA-353r-3v84-9pjj?

GHSA-353r-3v84-9pjj has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-353r-3v84-9pjj?

GHSA-353r-3v84-9pjj affects the following packages: nothing-js (npm). Ecosystems affected: npm.

How do I fix GHSA-353r-3v84-9pjj?

No patched version of nothing-js has shipped for GHSA-353r-3v84-9pjj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-353r-3v84-9pjj in my npm dependencies?

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

How do I mitigate GHSA-353r-3v84-9pjj 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-353r-3v84-9pjj actively exploited in the wild?

No public exploit code has been indexed for GHSA-353r-3v84-9pjj 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-353r-3v84-9pjj published, and has it been updated?

GHSA-353r-3v84-9pjj was published on September 1, 2020 and was last updated on October 1, 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 nothing-jsGHSA-353r-3v84-9pjj

CRITICAL

GHSA-353r-3v84-9pjj is a critical-severity (CVSS 9.8) vulnerability in nothing-js. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 1, 2020

Updated

Oct 1, 2021

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Oct 1, 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, a proxy for how much of the ecosystem is exposed.

nothing-jsnpm

5downloads / week

Description

nothing-js contained a malicious script that attempted to delete all files when npm test was run.

Recommendation

This module has been unpublished from the npm Registry. If you find this module in your environment remove it.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`nothing-js`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nothing-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of nothing-js has shipped for GHSA-353r-3v84-9pjj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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

`nothing-js` contained a malicious script that attempted to delete all files when `npm test` was run. ## Recommendation This module has been unpublished from the npm Registry. If you find this module in your environment remove it.

O3 Security · Impact-Aware SCA

Is GHSA-353r-3v84-9pjj in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works