Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

GHSA-mfc2-93pr-jf92

GHSA-mfc2-93pr-jf92 is a security vulnerability in loadyaml. O3 Security confirms whether GHSA-mfc2-93pr-jf92 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Malicious code in `loadyaml`

Published
Oct 1, 2020
Updated
Oct 1, 2020
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Oct 1, 2020 · 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.

loadyamlnpm
4downloads / week

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.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmloadyamlall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loadyaml. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of loadyaml has shipped for GHSA-mfc2-93pr-jf92 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-mfc2-93pr-jf92 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mfc2-93pr-jf92. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-mfc2-93pr-jf92 in your dependencies?

O3 detects GHSA-mfc2-93pr-jf92 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-mfc2-93pr-jf92: Malicious code in… | O3 Security