Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in agent-bot-api

Malware was discovered in the npm package agent-bot-api. Systems with this package installed or running should be considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with agent-bot-api installed or running
Ecosystems
Attack vectors
Affected entities
  • agent-bot-api

A critical malware incident was identified in the npm package agent-bot-api, disclosed via GitHub Advisory GHSA-wg39-r7v9-mwfc on August 17, 2026.\n\nAny computer with this package installed or running is considered fully compromised. The malware may have granted outside entities full control of affected systems.\n\nImmediate remediation requires rotating all secrets and keys from a separate, uncompromised computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the potential for full system compromise.\n\nUsers should assume that removing the package alone may be insufficient to fully remediate the compromise.

Indicators of compromise

Packages
  • agent-bot-api

Remediation

  • Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
  • Remove the agent-bot-api package from all affected systems
  • Conduct a full security audit and forensic analysis of any system that had this package installed
  • Monitor affected systems for signs of persistent compromise or lateral movement
  • Review access logs and audit trails for any unauthorized activity during the period the package was installed

Sources

  1. GitHub Advisory GHSA-wg39-r7v9-mwfc · GitHub Advisory Database

Cite this entry

"Malware in agent-bot-api." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 17, 2026; last updated August 17, 2026. https://supplychainattack.org/incident/malware-in-agent-bot-api-muot8c

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedcritical

    Malicious code in 3-buildsight-web (npm)

    The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.

    npmCompromised package
  2. resolvedcritical

    Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)

    Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.

    npmDependency confusionCompromised package
  3. resolvedcritical

    Malicious code in create-coin (npm)

    create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.

    npmCompromised packageTyposquatting
  4. resolvedcritical

    Malicious code in @syncraft-labs/vue (npm)

    The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.

    npmCompromised package