# MAL-2026-5462: Malicious code in @rockawayx/utils (npm)


- **Type:** Malicious package
- **Package:** `@rockawayx/utils` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-gj9m-m6gg-c8cx

## What is MAL-2026-5462?

MAL-2026-5462 is a malicious package in @rockawayx/utils, published on 9 Jun 2026. 

### Official description

@rockawayx/utils squats the unclaimed @rockawayx npm scope and runs a preinstall beacon on every install. package.json declares `"preinstall": "node notify.js || true"`; notify.js collects os.hostname(), os.userInfo().username, os.platform(), and a timestamp and POSTs them as JSON to https://2.25.140.71:8443/rockawayx/depconf-poc with `rejectUnauthorized: false` (TLS verification disabled). The destination is a hardcoded bare IPv4, not a publisher-owned domain. Any build that resolves @rockawayx/* against the public registry — the canonical dependency-confusion victim — will pull this package and silently transmit host identifiers to the bare IP. The README frames the package as authorized security research, but the code performs the same install-time exfiltration any dependency-confusion attacker would, and consumers in any pipeline (not only the targeted organization) trigger the beacon without consent.

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

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

## Sources

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

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