Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @e50/utils

The npm package @e50/utils was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with @e50/utils installed or running
Ecosystems
Attack vectors
Affected entities
  • @e50/utils

The npm package @e50/utils was identified as containing malware. According to the GitHub Advisory (GHSA-w945-prph-8545), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the malware may have granted outside entities full control of affected systems. While the package can 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.\n\nImmediate action is required for all affected systems, including rotation of all secrets and keys from a clean, unaffected computer.

Indicators of compromise

Packages
  • @e50/utils

Remediation

  • Immediately remove the @e50/utils package from all systems
  • Rotate all secrets, API keys, credentials, and tokens from a clean, unaffected computer
  • Perform a full security audit and malware scan of any system that had @e50/utils installed
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved

Sources

  1. GitHub Advisory GHSA-w945-prph-8545 · GitHub Advisory Database

Cite this entry

"Malware in @e50/utils." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-e50-utils-1o0hhq

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 sme-rko-finance-front-operations-feed-models (npm)

    The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.

    npmCompromised package
  2. resolvedcritical

    Malicious code in modern-localization (npm)

    The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().

    npmCompromised package
  3. resolvedcritical

    Malicious code in sme-rko-finance-front-operations-tax (npm)

    The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.

    npmCompromised package
  4. resolvedcritical

    Malicious code in localization-fixer (npm)

    The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.

    npmCompromised package