Which versions of crosswalker are malicious?

The following npm versions of crosswalker are flagged malicious: 1.0.0, 1.0.1, 18.2.1. Treat any of these as compromised.

How do I remediate crosswalker if I installed it?

crosswalker 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 crosswalker — how do I know if it already compromised me?

If crosswalker 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 crosswalker part of a known attack campaign?

Yes — crosswalker is associated with the RLMA-2024-00647, RLUA-2024-06366, IN-MAL-2026-007340 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 crosswalker 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 crosswalker (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging crosswalker across your stack and pipelines.

Malicious package

crosswalkernpm

Malicious code in crosswalker (npm) Remove it immediately and rotate any exposed credentials.

MAL-2024-2031

Immediate action

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

npm uninstall crosswalker

What this malware does

package.json declares preinstall: node index.js, causing index.js to run automatically on npm install. The script collects hostname, platform, arch, homedir, username, uid/gid, shell, OS info, cwd, and the output of whoami and id, then POSTs the JSON payload to a hardcoded URL at https://kbz9yyzq2mtljdwwf6r0tpzlfcl39txi.oastify.com/detox56. The destination is a Burp Collaborator subdomain — out-of-band infrastructure used to confirm exfiltration / RCE during dependency-confusion reconnaissance. Installer host and user identifiers leave the machine without consent on every install.

Malicious versions

3 flagged

1.0.01.0.118.2.1

Indicators of compromise (SHA-256)

148095f56bec9386ec4bc32f297a96280fb3915ba079baf9c7d8a614cfb36233

3836b56aa95dfca87e242dbd470349f3f9cf85007f4c9af2e333e7da622c99dc

b352c9c53fc71d511dae5d0fd8acc4462286092822d70e37dd413593f12bf0d3

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 crosswalker (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging crosswalker across your stack and pipelines.
If you installed it — respond
crosswalker 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 crosswalker 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 crosswalker 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. crosswalker on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 18.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-00647RLUA-2024-06366IN-MAL-2026-007340

References

npmjs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks crosswalker-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