Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious code in loadyaml

GHSA-mfc2-93pr-jf92

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm loadyaml

    Affected
    <= 1.0.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-mfc2-93pr-jf92

  2. Revision 1 · created ·

    Published from osv record GHSA-mfc2-93pr-jf92

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-mfc2-93pr-jf92

Advisory: Malicious code in `loadyaml`
IDs: GHSA-mfc2-93pr-jf92
Record: https://patchnext.com/advisories/ghsa-mfc2-93pr-jf92 (revision 2, source checked 26 Oct 2026, 12:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm loadyaml: affected <= 1.0.2

## Suggested inspection (read-only)
- `npm ls loadyaml --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on loadyaml.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-mfc2-93pr-jf92 (OSV record GHSA-mfc2-93pr-jf92 lists affected ranges: npm loadyaml >=0 <=1.0.2)
- Verified: https://github.com/advisories/GHSA-mfc2-93pr-jf92 (GitHub-reviewed advisory GHSA-mfc2-93pr-jf92 lists affected ranges: npm loadyaml >=0 <=1.0.2)

Commands are suggestions: review each one before running it.

Loading voting…