Which versions of @hrmony/organisationsverwaltung are malicious?

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

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

@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.

I already installed @hrmony/organisationsverwaltung — how do I know if it already compromised me?

If @hrmony/organisationsverwaltung 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/organisationsverwaltung part of a known attack campaign?

Yes — @hrmony/organisationsverwaltung is associated with the IN-MAL-2026-020657 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/organisationsverwaltung 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/organisationsverwaltung (version 7.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/organisationsverwaltung across your stack and pipelines.

Malicious package

@hrmony/organisationsverwaltungnpm

@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.

Malicious versions

1 flagged

7.99.0

Indicators of compromise (SHA-256)

78807365ee9728923ec2d5d103ce7f4562b21e2fc8185483b482bb5d2f79748d

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/organisationsverwaltung (version 7.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/organisationsverwaltung across your stack and pipelines.
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.
Did it already run?
If @hrmony/organisationsverwaltung 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/organisationsverwaltung 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/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-020657

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database