# MAL-2026-17249: Malicious code in @hrmony/account-management (npm)


- **Type:** Malicious package
- **Package:** `@hrmony/account-management` (npm)
- **Published:** 29 Sep 2026
- **Also known as:** GHSA-ppvh-5qcf-3gvr

## What is MAL-2026-17249?

MAL-2026-17249 is a malicious package in @hrmony/account-management, published on 29 Sep 2026. 

### Official description

The main module executes on require/import via a top-level await. It queries the AWS IMDSv2 metadata service at 169.254.169.254 to retrieve instance identity, IAM role temporary credentials, user-data, and network information; enumerates all of process.env; and recursively reads Kubernetes-mounted secrets from /var/run/secrets/. The collected data is POSTed to the hardcoded attacker-controlled endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_account-management. The package name uses a private-looking scope (@hrmony) and declares an unpinned dependency on @hrmony/kit-5, consistent with a dependency-confusion / scope-squat attack targeting an internal npm scope.

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-17249?

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-17249 is a malicious package: @hrmony/account-management (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-17249/ (Markdown: https://insights.sbomify.com/MAL-2026-17249/index.md)
```

## Sources

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

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