harmony-enablers-test-2026npm
Malicious code in harmony-enablers-test-2026 (npm) Remove it immediately and rotate any exposed credentials.
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.
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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for harmony-enablers-test-2026 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging harmony-enablers-test-2026 across your stack and pipelines.
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 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-enablers-test-2026 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-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.