Malicious code in harmony-app-toolkit (npm)
The npm package harmony-app-toolkit version 22.0.0 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with domains associated with malicious activity and executes commands consistent with malicious behavior.
- Disclosed
- Last updated
- Blast radius
- Unknown; depends on adoption of version 22.0.0
- Ecosystems
- Attack vectors
- Affected entities
- harmony-app-toolkit · 22.0.0
The OpenSSF Package Analysis project identified harmony-app-toolkit version 22.0.0 on npm as containing malicious code. The analysis determined the package exhibits two key indicators of compromise: communication with a domain associated with malicious activity, and execution of commands associated with malicious behavior.\n\nThe malicious package was cataloged in the OpenSSF's malicious-packages repository under identifier MAL-2026-14055. The advisory was published on 2026-08-15 via GitHub's advisory system.\n\nUsers who have installed or depend on harmony-app-toolkit version 22.0.0 should immediately remove or update the package to a known-safe version.
Indicators of compromise
- Packages
- harmony-app-toolkit@22.0.0
Remediation
- Remove harmony-app-toolkit version 22.0.0 from all environments
- Audit package.json and lock files for the presence of harmony-app-toolkit@22.0.0
- Update to a safe version of harmony-app-toolkit if available, or replace with an alternative package
- Review any systems that executed code from this package for signs of compromise
- Monitor for suspicious network connections or command execution originating from affected systems
Sources
- GitHub Advisory GHSA-qp2p-qrmg-36rq · GitHub Advisory Database
Cite this entry
"Malicious code in harmony-app-toolkit (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 15, 2026; last updated August 15, 2026. https://supplychainattack.org/incident/malicious-code-in-harmony-app-toolkit-npm-cstj7v
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- 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 - 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 - 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 - 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