Which versions of @hrmony/kit are malicious?

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

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

@hrmony/kit 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 — how do I know if it already compromised me?

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

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

Yes — @hrmony/kit is associated with the IN-MAL-2026-020668 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 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @hrmony/kit (version 1.99.0).

Part of a larger attack: @hrmony published 34 malicious packages. See the full campaign →

Malicious package

@hrmony/kitnpm

Advisory published Sep 29, 2026Updated Sep 29, 2026

@hrmony/kit is a confirmed malicious npm package (MAL-2026-17263) 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 (npm)

MAL-2026-17263

Immediate action

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

npm uninstall @hrmony/kit

What this malware does

On require/import, index.js contacts the EC2 Instance Metadata Service at 169.254.169.254 using an IMDSv2 token, enumerates the instance's IAM role security-credentials (including temporary AWS access key, secret, and session token), enumerates every entry in process.env, and recursively reads /var/run/secrets/ (Kubernetes projected service-account tokens and mounted secrets). The collected data is POSTed to the hardcoded endpoint https://hrnmn.dd.h4x.tv/save_instance_info_index. package.json also declares a preinstall hook (node scripts/check_setup.mjs) intended to run a sibling variant of the same payload (scripts/check-setup.mjs) that exfiltrates to https://hrnmn.dd.h4x.tv/save_instance_info_hook; a filename hyphen/underscore mismatch appears to prevent that lifecycle path from firing, but the payload is present in the tarball. The package exports no functional API — index.js contains only the exfiltration code, and package.json metadata (description 'bip bop I get your sip sop', author 'kuhuna') is a cover story. The.h4x.tv destination is unrelated to any legitimate publisher.

Malicious versions

1 flagged

1.99.0

Indicators of compromise (SHA-256)

6976b2f9327b9a181d77cd0597ef2f657575961a3d47ef8c57de1f6d4141503d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @hrmony/kit (version 1.99.0).
If you installed it — respond
@hrmony/kit 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 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

No. @hrmony/kit 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-020668

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @hrmony/kit-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