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?

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

If @rockawayx/utils 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 @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.

How do I find @rockawayx/utils 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 @rockawayx/utils (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @rockawayx/utils across your stack and pipelines.

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

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

Detect & block this

O3 blocks @rockawayx/utils-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