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 autbank-core (npm)

    The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.

    npmCompromised package
  2. resolvedcritical

    Malicious code in adxaa (npm)

    The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.

    npmCompromised package
  3. resolvedcritical

    Malicious code in upload-to-gcp (npm)

    upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.

    npmCompromised package
  4. resolvedcritical

    Malicious code in akamai-sensor (npm)

    A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.

    npmCompromised packageTyposquatting