Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in @settle-sea/supporting-documents

Malware discovered in the npm package @settle-sea/supporting-documents. Systems with this package installed are considered fully compromised with potential for complete system control by external entities.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • @settle-sea/supporting-documents

A malware-laden version of the npm package @settle-sea/supporting-documents has been identified and published to the npm registry. According to the GitHub Advisory (GHSA-f375-927m-428g), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised system. While the package should 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, as the attacker may have gained full control of the system.\n\nThis is a critical supply chain attack affecting the npm ecosystem, with potential impact on all users and systems that have installed or executed this package.

Indicators of compromise

Packages
  • @settle-sea/supporting-documents

Remediation

  • Immediately remove the @settle-sea/supporting-documents package from all affected systems
  • Rotate all secrets, API keys, and credentials from a clean, uncompromised computer
  • Perform a full security audit and malware scan of any system that had this package installed
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider the affected system(s) potentially compromised and plan for full rebuild if critical systems are involved
  • Monitor for any suspicious activity on accounts or systems that may have been exposed

Sources

  1. GitHub Advisory GHSA-f375-927m-428g · GitHub Advisory Database

Cite this entry

"Malware in @settle-sea/supporting-documents." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-settle-sea-supporting-documents-1vut7s

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