# GHSA-38vq-cjh5-vw7x: Malicious Package in nodes.js

> A malicious npm package installs thousands of dependencies to exhaust system memory, causing denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2020

## What is GHSA-38vq-cjh5-vw7x?

GHSA-38vq-cjh5-vw7x is a vulnerability in nodes.js, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `nodes.js ` contain malicious code. The package searches and installs globally thousands of packages based on keywords `node`, `react`, `react-native`, `vue`, `angular` and `babel` to fill the system's memory.

## Recommendation

Remove the package from your environment and validate what packages are installed.

## Which versions are affected by GHSA-38vq-cjh5-vw7x?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nodes.js` | npm | From 0.0.0 | None |
| `nodes.js` | npm | From 0.0.0 | None |

## How do I fix GHSA-38vq-cjh5-vw7x?

No fix has been published for GHSA-38vq-cjh5-vw7x yet. Limit exposure of the affected software until one is available.

## Is GHSA-38vq-cjh5-vw7x being exploited?

There is no known exploitation of GHSA-38vq-cjh5-vw7x in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-38vq-cjh5-vw7x and fix it if it is affected.

What it is: GHSA-38vq-cjh5-vw7x is a vulnerability in nodes.js, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-38vq-cjh5-vw7x in the wild and no public exploit code.

Affected packages and fixed versions:
- nodes.js (npm): affected from 0.0.0; no fix listed
- nodes.js (npm): affected from 0.0.0; 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-38vq-cjh5-vw7x/ (Markdown: https://insights.sbomify.com/GHSA-38vq-cjh5-vw7x/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-38vq-cjh5-vw7x

---
From sbomify Insights: https://insights.sbomify.com/GHSA-38vq-cjh5-vw7x/
Summaries are generated and may contain mistakes; the official description above is the record.