Which versions of @hrmony/devtool-configuration are malicious?

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

How do I remediate @hrmony/devtool-configuration if I installed it?

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

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

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

Malicious package

@hrmony/devtool-configurationnpm

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

MAL-2026-17260

Immediate action

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

npm uninstall @hrmony/devtool-configuration

What this malware does

On import, index.js performs an unconditional POST beacon to https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_devtool-configuration, then queries the AWS EC2 IMDSv2 endpoint (169.254.169.254) to collect the instance identity document, user-data, network/instance metadata, and IAM security-credentials (including access key, secret key, and session token) for every attached role, and POSTs the collected JSON to the same attacker host. It additionally enumerates process.env in full and recursively reads /var/run/secrets/ (Kubernetes service-account tokens and mounted secrets), sending both to the same endpoint. The destination host is unrelated to any AWS, Kubernetes, or npm publisher domain, and collection fires at module load with no caller opt-in.

Malicious versions

1 flagged

1.99.0

Indicators of compromise (SHA-256)

f83cb569df9c47639ee0fd16c34a4ac1b97b89733b1b468389d8032087ab233b

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/devtool-configuration (version 1.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/devtool-configuration across your stack and pipelines.
If you installed it — respond
@hrmony/devtool-configuration 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/devtool-configuration 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/devtool-configuration 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/devtool-configuration 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-020637

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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