NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @hrmony published 34 malicious packages. See the full campaign →
Malicious package

@hrmony/component-librarynpm

Advisory published Updated

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

Malicious code in @hrmony/component-library (npm)

MAL-2026-17259
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @hrmony/component-library

What this malware does

index.js (declared as the package main) runs top-level async code on require/import that performs three exfiltration actions against a hardcoded attacker endpoint https://hrnmn.dd.h4x.tv/. First, it POSTs a fixed beacon identifying the package to /save_instance_info_from_pkge_hrmony_component-library. Second, it queries the AWS EC2 Instance Metadata Service at 169.254.169.254 using IMDSv2, enumerates IAM roles, and reads iam/security-credentials/{role} to collect temporary AWS access keys along with the identity document and user-data, then POSTs the collected object to the same host. Third, it iterates every entry of process.env and recursively reads all files under /var/run/secrets/ (Kubernetes service-account tokens and mounted secrets) and POSTs them to the same host. The package ships no component-library code; the exfiltration payload is its only behavior. The scope name @hrmony (missing the 'a' from @harmony) and the abnormally high 28.99.0 version are consistent with typosquat and dependency-confusion targeting.

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.

Malicious versions

1 flagged
28.99.0

Indicators of compromise (SHA-256)

a93efe09ed89a9899669e54f614f80d91a80c59d77e0c2a2f673f92590488804
43173bc756c5c7bb307d748364b7436b5691bd972fa14c3ab6f51a4a510aeafd

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @hrmony/component-library (version 28.99.0).

  2. If you installed it — respond

    @hrmony/component-library 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.

  3. Did it already run?

    If @hrmony/component-library 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/component-library on npm has been identified as a malicious package (version 28.99.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020651GHSA-cjfr-hq8x-q26q

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

@hrmony/component-library (npm) malicious package — MAL-2026-17259 | O3 Security