Vulnerabilities in pkg:npm/boogeyman
PACKAGEGHSA-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.
pkg:npm/boogeyman
Vulnerability advisories affecting package pkg:npm/boogeyman. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-9hc2-w9gg-q6jw | - | CRITICAL | Malicious Package in boogeyman |
GHSA-9hc2-w9gg-q6jw at a Glance
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).
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.
npm install boogeyman@Latest secure release
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
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?
Which Boogeyman versions are affected?
What version fixes GHSA-9hc2-w9gg-q6jw?
Is boogeyman affected?
What is the CVSS score of GHSA-9hc2-w9gg-q6jw?
What CWE is associated with GHSA-9hc2-w9gg-q6jw?
How can I check npm dependencies for GHSA-9hc2-w9gg-q6jw?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"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
}
}