Which versions of @hrmony/kit-1 are malicious?

The following npm versions of @hrmony/kit-1 are flagged malicious: 1.99.0. Treat any of these as compromised.

How do I remediate @hrmony/kit-1 if I installed it?

@hrmony/kit-1 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @hrmony/kit-1 — how do I know if it already compromised me?

If @hrmony/kit-1 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.

Is @hrmony/kit-1 part of a known attack campaign?

Yes — @hrmony/kit-1 is associated with the IN-MAL-2026-020669 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @hrmony/kit-1 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @hrmony/kit-1 (version 1.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/kit-1 across your stack and pipelines.

Malicious package

@hrmony/kit-1npm

@hrmony/kit-1 is a confirmed malicious npm package (MAL-2026-17264) that steals credentials and exfiltrates sensitive data (malicious version 1.99.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @hrmony/kit-1 (npm)

MAL-2026-17264

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @hrmony/kit-1

What this malware does

The package executes credential-harvesting code both from its postinstall script (scripts/check-setup.mjs) and from its main entry (index.js), so theft fires on npm install and again on require/import even when lifecycle scripts are skipped. Both code paths query the EC2 Instance Metadata Service at 169.254.169.254 (IMDSv2 token flow) to retrieve instance identity, IAM role names, and the role's temporary security credentials; enumerate all of process.env; and recursively read /var/run/secrets/ (Kubernetes service-account tokens and mounted secrets). The collected data is POSTed to https://hrmnmn.dd.h4x.tv/save_instance_info_hook and https://hrmnmn.dd.h4x.tv/save_instance_info_index. An additional unconditional beacon POST ({"c53":"hello"}) to the same host provides install/import telemetry. The h4x.tv destination has no relation to any declared publisher or purpose.

Malicious versions

1 flagged

1.99.0

Indicators of compromise (SHA-256)

0a4084c44ab6554d66c474338de2cb482a25b31e6822d470e08b2b2ef5b1735a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @hrmony/kit-1 (version 1.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/kit-1 across your stack and pipelines.
If you installed it — respond
@hrmony/kit-1 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @hrmony/kit-1 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 @hrmony/kit-1 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

No. @hrmony/kit-1 on npm has been identified as a malicious package (version 1.99.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020669

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @hrmony/kit-1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database