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/organisationsverwaltungnpm

Advisory published Updated

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

Malicious code in @hrmony/organisationsverwaltung (npm)

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

What this malware does

@hrmony/organisationsverwaltung 7.99.0 executes credential-theft code at the top level of index.js, so simply requiring or importing the package triggers exfiltration. On load it sends a hello beacon via POST to https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_organisationsverwaltung, then queries the AWS EC2 Instance Metadata Service at 169.254.169.254 (IMDSv2) to retrieve IAM role security-credentials and identity documents, enumerates all entries of process.env, and recursively reads every file under /var/run/secrets/ (the mount path for Kubernetes service-account tokens and mounted secrets). The collected AWS credentials, environment variables, and Kubernetes secrets are POSTed as a JSON payload to the same hardcoded endpoint at hrnmn.dd.h4x.tv. Package metadata (empty description, no repository, version 7.99.0 published under the @hrmony scope with a self-declared @hrmony/kit-5 dependency) is consistent with a dependency-confusion package targeting an internal @hrmony/* namespace.

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
7.99.0

Indicators of compromise (SHA-256)

78807365ee9728923ec2d5d103ce7f4562b21e2fc8185483b482bb5d2f79748d
078cf96d70a32e670e25a0be40b81d1d8e95bbffc9ccb5129a174c61e21b8fcd

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @hrmony/organisationsverwaltung (version 7.99.0).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-020657GHSA-gxrr-r3q5-4429

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @hrmony/organisationsverwaltung-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/organisationsverwaltung (npm) malicious package — MAL-2026-17270 | O3 Security