Vulnerabilities in pkg:npm/loadyaml

PACKAGE
Advisory Summary

GHSA-mfc2-93pr-jf92 is a CRITICAL malicious code vulnerability (CWE-506: Embedded Malicious Code) affecting Loadyaml libraries in the npm ecosystem. The issue involves malicious code in `loadyaml`. Remediation is available in the latest vendor maintenance releases.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/loadyaml

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/loadyaml. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-mfc2-93pr-jf92 - CRITICAL Malicious code in `loadyaml`

GHSA-mfc2-93pr-jf92 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-mfc2-93pr-jf92
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Loadyaml
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-mfc2-93pr-jf92

To remediate this vulnerability, upgrade all affected Loadyaml dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

loadyaml fixed: Latest secure release
npm install loadyaml@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls loadyaml

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-mfc2-93pr-jf92, inspect your project dependencies using npm:

npm ls loadyaml

Analyze the terminal output to locate any version of Loadyaml in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The npm ls loadyaml command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-506: Embedded Malicious Code, where the product contains code that appears to be malicious in nature. In Loadyaml, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

GHSA-mfc2-93pr-jf92 Affected Loadyaml Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
loadyaml
npm
≤ 1.0.2

References

Frequently Asked Questions

What is GHSA-mfc2-93pr-jf92?
GHSA-mfc2-93pr-jf92 is a security vulnerability in Loadyaml involving Malicious code in `loadyaml` under CWE-506: Embedded Malicious Code.
Which Loadyaml versions are affected?
Affected versions include releases prior to current release patches across affected packages: loadyaml.
What version fixes GHSA-mfc2-93pr-jf92?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is loadyaml affected?
Yes, loadyaml is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-mfc2-93pr-jf92?
GHSA-mfc2-93pr-jf92 is classified under CWE-506: Embedded Malicious Code (The product contains code that appears to be malicious in nature.).
How can I check npm dependencies for GHSA-mfc2-93pr-jf92?
Run the dependency tree command: 'npm ls loadyaml'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mfc2-93pr-jf92",
  "modified" : "2020-10-01T17:09:29Z",
  "published" : "2020-10-01T17:10:15Z",
  "aliases" : [ ],
  "summary" : "Malicious code in `loadyaml`",
  "details" : "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:\n- IP and IP-based geolocation\n- home directory name\n- local username \n\nThe malicious packages have been removed from the npm registry and the leaked content removed from GitHub.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "loadyaml"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "1.0.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/1563"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-10-01T17:09:29Z",
    "nvd_published_at" : null
  }
}