Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @engagehub/core

Malware was discovered in the npm package @engagehub/core. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with @engagehub/core installed
Ecosystems
Attack vectors
Affected entities
  • @engagehub/core

A malware incident was identified in the npm package @engagehub/core, published via GitHub Advisory GHSA-5hgc-pmxv-3xh7 on July 7, 2026.\n\nAny computer with this package installed or running should be considered fully compromised. The malware grants full control of the affected system to an outside entity.\n\nImmediate remediation is required: all secrets and keys stored on affected computers must be rotated from a different, uncompromised system. The package should be removed, though complete removal of all malicious software cannot be guaranteed due to the level of system compromise.\n\nThis represents a critical supply chain attack through package distribution.

Indicators of compromise

Packages
  • @engagehub/core

Remediation

  • Immediately rotate all secrets and keys from a different, uncompromised computer
  • Remove the @engagehub/core package from all affected systems
  • Audit system logs for unauthorized access or activity
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
  • Check for any other suspicious packages or modifications on affected systems

Sources

  1. GitHub Advisory GHSA-5hgc-pmxv-3xh7 · GitHub Advisory Database

Cite this entry

"Malware in @engagehub/core." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 7, 2026; last updated July 7, 2026. https://supplychainattack.org/incident/malware-in-engagehub-core-15mt8h

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