Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @gocortexio/npmgremlinbox-malware-c2-beacon

A malicious npm package @gocortexio/npmgremlinbox-malware-c2-beacon was published, containing a C2 beacon that grants full system compromise to attackers. Any system with this package installed should be considered fully compromised.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • @gocortexio/npmgremlinbox-malware-c2-beacon

A malicious npm package named @gocortexio/npmgremlinbox-malware-c2-beacon was identified and published to the npm registry. The package contains malware that establishes a command-and-control (C2) beacon on infected systems.

According to the GitHub Advisory (GHSA-vmcc-vqgj-wh6c), any computer that has this package installed or running should be considered fully compromised. The malware grants outside entities full control of the affected system.

Immediate remediation requires rotating all secrets and keys from a different, uncompromised computer. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given the level of system access the malware achieves.

Users should assume complete system compromise and take appropriate incident response measures.

Indicators of compromise

Packages
  • @gocortexio/npmgremlinbox-malware-c2-beacon

Remediation

  • Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
  • Remove the @gocortexio/npmgremlinbox-malware-c2-beacon package from all affected systems
  • Assume full system compromise and conduct thorough forensic analysis
  • Monitor affected systems for signs of persistent malware or backdoors
  • Consider rebuilding affected systems from clean media if critical infrastructure is involved
  • Audit all activities and access logs from affected systems during the compromise period

Sources

  1. GitHub Advisory GHSA-vmcc-vqgj-wh6c · GitHub Advisory Database

Cite this entry

"Malware in @gocortexio/npmgremlinbox-malware-c2-beacon." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 20, 2026; last updated July 20, 2026. https://supplychainattack.org/incident/malware-in-gocortexio-npmgremlinbox-malware-c2-beacon-1xjek6

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. resolvedcritical

    Malicious code in test2221 (npm)

    The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.

    npmCompromised package
  2. containedcritical

    Malware in n8n-nodes-trust-me-im-totally-safe

    Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.

    npmCompromised package
  3. activecritical

    Malware in litespeed-cache

    Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.

    npmCompromised package
  4. containedcritical

    Malware in open-worker-cli

    Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.

    npmCompromised package