harmony-app-toolkitnpm
harmony-app-toolkit is a confirmed malicious npm package (MAL-2026-14055) that executes malicious code on install (malicious versions 21.0.0, 22.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in harmony-app-toolkit (npm)
What this malware does
The package declares a preinstall lifecycle script (preinstall.js) that reads a hex-encoded command from preinstall.json, decodes it with Buffer.from(hex,'hex'), and passes the result to child_process.exec. The decoded command shells out via curl to https://eousft8gflamm91.m.pipedream.net and POSTs the output of whoami, pwd, hostname, and the contents of /etc/passwd from the installing host. The behavior runs automatically on npm install, uses hex encoding to hide the payload string, and sends installer host identity and a system account file to an attacker-controlled Pipedream endpoint.
The OpenSSF Package Analysis project identified 'harmony-app-toolkit' @ 22.0.0 (npm) as malicious.
It is considered malicious because:
-
The package communicates with a domain associated with malicious activity.
-
The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for harmony-app-toolkit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging harmony-app-toolkit across your stack and pipelines.
If you installed it — respond
Remove harmony-app-toolkit from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If harmony-app-toolkit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks harmony-app-toolkit before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks harmony-app-toolkit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.