Which versions of @hrmony/middlewares are malicious?

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

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

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

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

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

Malicious package

@hrmony/middlewaresnpm

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

Malicious code in @hrmony/middlewares (npm)

MAL-2026-17269

Immediate action

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

npm uninstall @hrmony/middlewares

What this malware does

On module load, the package queries the AWS instance metadata service at 169.254.169.254 (IMDSv2) to enumerate instance identity, region, and network interfaces, then iterates IAM role security-credentials to retrieve temporary AWS access keys. It additionally serializes all entries of process.env and recursively reads Kubernetes service-account secret files under /var/run/secrets/. The aggregated payload is POSTed to the hardcoded endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_middlewares. The package name '@hrmony/middlewares' is a lookalike of '@harmony/middlewares' (dropped 'a'), and the exfiltration host 'hrnmn.dd.h4x.tv' mirrors the same abbreviation pattern. No legitimate functionality is provided; the module's sole install/import-time effect is credential and secret exfiltration.

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

3.99.0

Indicators of compromise (SHA-256)

2129e9ecca729ffb0ac23ee07dd5be18f2a853560899599981bc92b19dda4363

5ef2211704616afd6477e55b46d6ae191d7558da7cd4c5f1b212a13d7489f9f4

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/middlewares (version 3.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/middlewares across your stack and pipelines.
If you installed it — respond
@hrmony/middlewares 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/middlewares 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/middlewares 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/middlewares on npm has been identified as a malicious package (version 3.99.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020653GHSA-5cwm-5j38-r753

References

Credits

Amazon Inspector · finder

Detect & block this

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