# GHSA-5fm9-jmv7-fcx5: Malicious Package in asynnc

> A typosquatted npm package exfiltrates installation metadata to a remote server, requiring developers to remove the malicious dependency.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Sep 2020

## What is GHSA-5fm9-jmv7-fcx5?

GHSA-5fm9-jmv7-fcx5 is a vulnerability in asynnc, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

All versions of `asynnc` typosquatted a popular package of similar name and tracked users who had installed the incorrect package. The package uploaded information to a remote server including: name of the downloaded package, name of the intended package, the Node version and whether the process was running as sudo. There is no further compromise.

## Recommendation

Remove the package from your dependencies and always ensure package names are typed correctly upon installation.

## Which versions are affected by GHSA-5fm9-jmv7-fcx5?

2 open source packages ship an affected version, including asynnc.


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

## How do I fix GHSA-5fm9-jmv7-fcx5?

No fix has been published for GHSA-5fm9-jmv7-fcx5 yet. Limit exposure of the affected software until one is available.

## Is GHSA-5fm9-jmv7-fcx5 being exploited?

There is no known exploitation of GHSA-5fm9-jmv7-fcx5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-5fm9-jmv7-fcx5 and fix it if it is affected.

What it is: GHSA-5fm9-jmv7-fcx5 is a vulnerability in asynnc, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-5fm9-jmv7-fcx5 in the wild and no public exploit code.

Affected packages and fixed versions:
- asynnc (npm): affected all versions; no fix listed
- asynnc (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-5fm9-jmv7-fcx5/ (Markdown: https://insights.sbomify.com/GHSA-5fm9-jmv7-fcx5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-5fm9-jmv7-fcx5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-5fm9-jmv7-fcx5/
Summaries are generated and may contain mistakes; the official description above is the record.