Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @gocortexio/npmgremlinbox-cc-by-nd-3-0-de

Malware was distributed via the npm package @gocortexio/npmgremlinbox-cc-by-nd-3-0-de, providing full system compromise to any computer with the package installed or running. All affected systems should be considered fully compromised and all secrets and keys rotated immediately from a different computer.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • @gocortexio/npmgremlinbox-cc-by-nd-3-0-de

A malicious npm package @gocortexio/npmgremlinbox-cc-by-nd-3-0-de was identified and published to the npm registry. The package contains malware that grants full control of the affected system to an outside entity.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised computer.

While the package should be removed, there is no guarantee that removal will eliminate all malicious software resulting from the installation, as the attacker may have gained full system control. A comprehensive security review and potential system rebuild may be necessary for affected systems.

Indicators of compromise

Packages
  • @gocortexio/npmgremlinbox-cc-by-nd-3-0-de

Remediation

  • Immediately identify all systems with @gocortexio/npmgremlinbox-cc-by-nd-3-0-de installed or running
  • Isolate affected systems from the network
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the package from all affected systems
  • Conduct a full security audit and malware scan of affected systems
  • Consider rebuilding affected systems from clean media if full compromise is suspected
  • Review logs and audit trails for any unauthorized access or data exfiltration
  • Monitor for any persistence mechanisms left by the malware

Sources

  1. GitHub Advisory GHSA-66vh-6mm9-hgp5 · GitHub Advisory Database

Cite this entry

"Malware in @gocortexio/npmgremlinbox-cc-by-nd-3-0-de." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 20, 2026; last updated July 20, 2026. https://supplychainattack.org/incident/malware-in-gocortexio-npmgremlinbox-cc-by-nd-3-0-de-1x18vd

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