GHSA-4xg9-g7qj-jhg4: Comander Malicious Package Vulnerability

CRITICAL
CVSS 9.8
CWE-506
Published
Advisory Summary

GHSA-4xg9-g7qj-jhg4 is a CRITICAL (CVSS 9.8) malicious package vulnerability (CWE-506: Embedded Malicious Code) affecting Comander libraries in the npm ecosystem. The issue involves malicious package in comander. Remediation is available in the latest vendor maintenance releases.

GHSA-4xg9-g7qj-jhg4 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-4xg9-g7qj-jhg4
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Comander
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-4xg9-g7qj-jhg4

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

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

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-4xg9-g7qj-jhg4, inspect your project dependencies using npm:

npm ls comander

Analyze the terminal output to locate any version of Comander 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 comander 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 Comander, 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 `comander` contains malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive. ## Recommendation Remove the package from your environment and verify whether your system is running the cryptocurrency miner.

GHSA-4xg9-g7qj-jhg4 Affected Comander Versions

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

References

Frequently Asked Questions

What is GHSA-4xg9-g7qj-jhg4?
GHSA-4xg9-g7qj-jhg4 is a security vulnerability in Comander involving Malicious Package in comander under CWE-506: Embedded Malicious Code.
Which Comander versions are affected?
Affected versions include releases prior to current release patches across affected packages: comander.
What version fixes GHSA-4xg9-g7qj-jhg4?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is comander affected?
Yes, comander 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-4xg9-g7qj-jhg4?
GHSA-4xg9-g7qj-jhg4 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-4xg9-g7qj-jhg4?
GHSA-4xg9-g7qj-jhg4 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-4xg9-g7qj-jhg4?
Run the dependency tree command: 'npm ls comander'. 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-4xg9-g7qj-jhg4",
  "modified" : "2021-09-29T20:33:40Z",
  "published" : "2020-09-03T20:46:36Z",
  "aliases" : [ ],
  "summary" : "Malicious Package in comander",
  "details" : "All versions of `comander` contains malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.\n\n\n## Recommendation\n\nRemove the package from your environment and verify whether your system is running the cryptocurrency miner.",
  "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" : "comander"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/1193"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-08-31T18:50:38Z",
    "nvd_published_at" : null
  }
}