GHSA-9hc2-w9gg-q6jw: Boogeyman Malicious Package Vulnerability

CRITICAL
CVSS 9.8
CWE-506
Published
Advisory Summary

GHSA-9hc2-w9gg-q6jw is a CRITICAL (CVSS 9.8) malicious package vulnerability (CWE-506: Embedded Malicious Code) affecting Boogeyman libraries in the npm ecosystem. The issue involves malicious package in boogeyman. Remediation is available in the latest vendor maintenance releases.

GHSA-9hc2-w9gg-q6jw at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-9hc2-w9gg-q6jw
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Boogeyman
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix GHSA-9hc2-w9gg-q6jw

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

boogeyman fixed: Latest secure release
npm install boogeyman@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 boogeyman

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-9hc2-w9gg-q6jw, inspect your project dependencies using npm:

npm ls boogeyman

Analyze the terminal output to locate any version of Boogeyman 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 boogeyman 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 Boogeyman, 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

All versions of `boogeyman` are considered malicious. This particular package would download a payload from pastebin.com, eval it to read ssh keys and the users `.npmrc` and send them to a private pastebin account. ## Recommendation This package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate your ssh keys and your npm token.

GHSA-9hc2-w9gg-q6jw Affected Boogeyman Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
boogeyman
npm
≥ 0.0.0

References

Frequently Asked Questions

What is GHSA-9hc2-w9gg-q6jw?
GHSA-9hc2-w9gg-q6jw is a security vulnerability in Boogeyman involving Malicious Package in boogeyman under CWE-506: Embedded Malicious Code.
Which Boogeyman versions are affected?
Affected versions include releases prior to current release patches across affected packages: boogeyman.
What version fixes GHSA-9hc2-w9gg-q6jw?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is boogeyman affected?
Yes, boogeyman is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of GHSA-9hc2-w9gg-q6jw?
GHSA-9hc2-w9gg-q6jw has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with GHSA-9hc2-w9gg-q6jw?
GHSA-9hc2-w9gg-q6jw 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-9hc2-w9gg-q6jw?
Run the dependency tree command: 'npm ls boogeyman'. 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-9hc2-w9gg-q6jw",
  "modified" : "2021-10-01T13:28:13Z",
  "published" : "2020-09-01T21:07:41Z",
  "aliases" : [ ],
  "summary" : "Malicious Package in boogeyman",
  "details" : "All versions of `boogeyman` are considered malicious. This particular package would download a payload from pastebin.com, eval it to read ssh keys and the users `.npmrc` and send them to a private pastebin account.\n\n\n## Recommendation\n\nThis package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate your ssh keys and your npm token.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "boogeyman"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/677"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-08-31T18:32:24Z",
    "nvd_published_at" : null
  }
}