harmony-enablers-test-2026npm
Advisory published Updated
harmony-enablers-test-2026 is a confirmed malicious npm package (MAL-2026-4251) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in harmony-enablers-test-2026 (npm)
What this malware does
On npm install, the package.json preinstall hook runs node telemetry.js, which performs a DNS lookup against test-callback.d87u1z3.oast.live — an Interactsh out-of-band interaction listener. The lookup fires automatically without consent and signals to the operator of the OAST host that the package landed inside the installer's environment, leaking the installer's resolver IP and confirming reachability. The package self-describes as a dependency-confusion proof-of-concept, and the install-time beacon is the attacker-benefit mechanism: it tells the publisher which organizations are vulnerable to namespace confusion against this name. No legitimate purpose exists for an install-time DNS callback to an OAST listener.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
The OpenSSF Package Analysis project identified 'harmony-enablers-test-2026' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for harmony-enablers-test-2026 (version 1.0.0).
If you installed it — respond
harmony-enablers-test-2026 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If harmony-enablers-test-2026 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks harmony-enablers-test-2026-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.