# GHSA-mfc2-93pr-jf92: Malicious code in `loadyaml`

> Malicious npm packages leak user IP, location, and username to GitHub upon installation, requiring removal of affected dependencies.

- **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:** 1 Oct 2020

## What is GHSA-mfc2-93pr-jf92?

GHSA-mfc2-93pr-jf92 is a vulnerability in loadyaml, published on 1 Oct 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

npm packages `loadyaml` and `electorn` were removed from the npm registry for containing malicious code. Upon installation the package runs a preinstall script that writes a public comment on GitHub containing the following information:
- IP and IP-based geolocation
- home directory name
- local username 

The malicious packages have been removed from the npm registry and the leaked content removed from GitHub.

## Which versions are affected by GHSA-mfc2-93pr-jf92?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `loadyaml` | npm | All versions to 1.0.2 | None |
| `loadyaml` | npm | All versions to 1.0.2 | None |

## How do I fix GHSA-mfc2-93pr-jf92?

No fix has been published for GHSA-mfc2-93pr-jf92 yet. Limit exposure of the affected software until one is available.

## Is GHSA-mfc2-93pr-jf92 being exploited?

There is no known exploitation of GHSA-mfc2-93pr-jf92 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-mfc2-93pr-jf92 and fix it if it is affected.

What it is: GHSA-mfc2-93pr-jf92 is a vulnerability in loadyaml, published on 1 Oct 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-mfc2-93pr-jf92 in the wild and no public exploit code.

Affected packages and fixed versions:
- loadyaml (npm): affected all versions up to 1.0.2; no fix listed
- loadyaml (npm): affected all versions up to 1.0.2; 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-mfc2-93pr-jf92/ (Markdown: https://insights.sbomify.com/GHSA-mfc2-93pr-jf92/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-mfc2-93pr-jf92

---
From sbomify Insights: https://insights.sbomify.com/GHSA-mfc2-93pr-jf92/
Summaries are generated and may contain mistakes; the official description above is the record.