Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

r4wk-booknpm

Advisory published Updated

r4wk-book is a confirmed malicious npm package (MAL-2026-14509) that executes malicious code on install (malicious version 2.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in r4wk-book (npm)

MAL-2026-14509
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall r4wk-book

What this malware does

On npm install, the package's postinstall hook runs node.worker.js, which detaches a background child, waits a jittered delay, and opens a TCP socket to a base64-encoded host:port literal that decodes to 172.16.42.138:1234. It then spawns /bin/sh -i (or cmd.exe on Windows) and pipes the socket to the shell's stdin and the shell's stdout back to the socket, giving whoever controls that address an interactive shell on the installer's machine. The destination is stored as Buffer.from('MTcyLjE2LjQyLjEzODoxMjM0Cg==','base64').toString().split(':') rather than a plain literal, concealing the endpoint. The package.json advertises a generic purpose ("Background sync module for legacy systems") and declares itself as its own dependency (r4wk-book: ^2.2.1), consistent with a throwaway lure rather than a functional library.

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.

Malicious versions

1 flagged
2.2.2

Indicators of compromise (SHA-256)

fca7aeb2a2052ce1bdd6d78ef66f735c8a3f1ab10b00d07d6e9dae8189722728
7f5cbca68751eb879140f7c896a0dc3c324e9f4dbc8a1651b38b246b299ba4eb

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for r4wk-book (version 2.2.2).

  2. If you installed it — respond

    Remove r4wk-book 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 activity or persistence.

  3. Did it already run?

    If r4wk-book was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. r4wk-book on npm has been identified as a malicious package (version 2.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jqfp-p3qc-cqm9IN-MAL-2026-018739

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks r4wk-book-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

r4wk-book (npm) malicious package — MAL-2026-14509 | O3 Security