# GHSA-353r-3v84-9pjj: Malicious Package in nothing-js

> A malicious npm package deletes files during test execution, requiring developers to remove the compromised library from their projects.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Sep 2020

## What is GHSA-353r-3v84-9pjj?

GHSA-353r-3v84-9pjj is a vulnerability in nothing-js, published on 1 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

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

2 open source packages ship an affected version, including nothing-js.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nothing-js` | npm | All versions | None |
| `nothing-js` | npm | All versions | None |

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

No fix has been published for GHSA-353r-3v84-9pjj yet. Limit exposure of the affected software until one is available.

## Is GHSA-353r-3v84-9pjj being exploited?

There is no known exploitation of GHSA-353r-3v84-9pjj in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-353r-3v84-9pjj and fix it if it is affected.

What it is: GHSA-353r-3v84-9pjj is a vulnerability in nothing-js, published on 1 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-353r-3v84-9pjj in the wild and no public exploit code.

Affected packages and fixed versions:
- nothing-js (npm): affected all versions; no fix listed
- nothing-js (npm): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-353r-3v84-9pjj/ (Markdown: https://insights.sbomify.com/GHSA-353r-3v84-9pjj/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-353r-3v84-9pjj

---
From sbomify Insights: https://insights.sbomify.com/GHSA-353r-3v84-9pjj/
Summaries are generated and may contain mistakes; the official description above is the record.