# MAL-2026-17260: Malicious code in @hrmony/devtool-configuration (npm)


- **Type:** Malicious package
- **Package:** `@hrmony/devtool-configuration` (npm)
- **Published:** 29 Sep 2026
- **Also known as:** GHSA-qh4w-rc3m-9898

## What is MAL-2026-17260?

MAL-2026-17260 is a malicious package in @hrmony/devtool-configuration, published on 29 Sep 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-17260?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17260 is a malicious package: @hrmony/devtool-configuration (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17260/ (Markdown: https://insights.sbomify.com/MAL-2026-17260/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17260

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17260/
Summaries are generated and may contain mistakes; the official description above is the record.