GHSA-4XG9-G7QJ-JHG4

GHSA-4XG9-G7QJ-JHG4 is a critical-severity security vulnerability in comander (npm), affecting versions >= 0.0.0. No fixed version is listed yet.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Malicious Package in comander

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.

Impact

GHSA-4XG9-G7QJ-JHG4 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

comander (>= 0.0.0)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Remove the package from your environment and verify whether your system is running the cryptocurrency miner.

Frequently Asked Questions

  1. What is GHSA-4XG9-G7QJ-JHG4? GHSA-4XG9-G7QJ-JHG4 is a critical-severity security vulnerability in comander (npm), affecting versions >= 0.0.0. No fixed version is listed yet.
  2. How severe is GHSA-4XG9-G7QJ-JHG4? GHSA-4XG9-G7QJ-JHG4 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of comander are affected by GHSA-4XG9-G7QJ-JHG4? comander (npm) versions >= 0.0.0 is affected.
  4. Is there a fix for GHSA-4XG9-G7QJ-JHG4? No fixed version is listed for GHSA-4XG9-G7QJ-JHG4 yet. Monitor the advisory for updates and apply mitigations in the interim.
  5. Is GHSA-4XG9-G7QJ-JHG4 exploitable, and should I be worried? Whether GHSA-4XG9-G7QJ-JHG4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether GHSA-4XG9-G7QJ-JHG4 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Stop the waste.
Protect your environment with Kodem.