Which versions of @rockawayx/utils are malicious?

The following npm versions of @rockawayx/utils are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate @rockawayx/utils if I installed it?

Remove @rockawayx/utils from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is @rockawayx/utils part of a known attack campaign?

Yes — @rockawayx/utils is associated with the IN-MAL-2026-005196 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect @rockawayx/utils in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @rockawayx/utils and packages like it before any post-install script runs.

Malicious package

@rockawayx/utilsnpm

Malicious code in @rockawayx/utils (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5462

Immediate action

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

npm uninstall @rockawayx/utils

What this malware does

@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.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e286c45b54ab9002ef8b7eec7ec686afc0bb82c2867c3640c460c8d1052b2bab

Frequently asked questions

No. @rockawayx/utils on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005196

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection