Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malware in poc-publish-test-su-doughnym

Malware was discovered in the npm package poc-publish-test-su-doughnym. Any computer with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different system.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • poc-publish-test-su-doughnym

A malicious npm package named poc-publish-test-su-doughnym was identified and published to the npm registry. The package contains malware that grants full control of affected systems to an outside entity.\n\nAny computer that has installed or executed this package should be considered fully compromised. All secrets, keys, and credentials stored on affected systems must be rotated immediately from a different, uncompromised computer.\n\nWhile the package should be removed, complete remediation cannot be guaranteed due to the potential for the malware to have established persistent access or additional backdoors on the compromised system.\n\nThe incident was disclosed via GitHub Advisory GHSA-fg75-hmqx-qfw9 on 2026-06-25.

Indicators of compromise

Packages
  • poc-publish-test-su-doughnym

Remediation

  • Immediately remove the poc-publish-test-su-doughnym package from all systems
  • Rotate all secrets, API keys, credentials, and tokens from a different, uncompromised computer
  • Conduct a full security audit of any system that had this package installed
  • Monitor affected systems for signs of persistent malware or unauthorized access
  • Review package dependencies to identify any other potentially compromised packages
  • Consider full system reimaging if the package was installed on production or sensitive systems

Sources

  1. GitHub Advisory GHSA-fg75-hmqx-qfw9 · GitHub Advisory Database

Cite this entry

"Malware in poc-publish-test-su-doughnym." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 25, 2026. https://supplychainattack.org/incident/malware-in-poc-publish-test-su-doughnym-18aya8

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