Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in ecto_module

Malware discovered in the npm package ecto_module. Systems with this package installed or running should be considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • ecto_module

A malware advisory was published for the npm package ecto_module on GitHub (GHSA-qj3m-j6gv-53pg). The advisory indicates that any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. The package should be removed, though there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for complete system compromise.

Indicators of compromise

Packages
  • ecto_module

Remediation

  • Immediately isolate any system with ecto_module installed from the network
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the ecto_module package from all affected systems
  • Conduct a full forensic analysis of affected systems to identify any additional malicious software
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider full system reimaging if complete compromise is suspected

Sources

  1. GitHub Advisory GHSA-qj3m-j6gv-53pg · GitHub Advisory Database

Cite this entry

"Malware in ecto_module." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 15, 2026; last updated June 16, 2026. https://supplychainattack.org/incident/malware-in-ecto-module-nrdil0

Suggest a correction

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

  1. 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
  2. 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
  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. activecritical

    Malware in def-open-client

    The npm package def-open-client contains malware that provides full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package