r4wk-book@2.2.2

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. ## Source: ghsa-malware (fca7aeb2a2052ce1bdd6d78ef66f735c8a3f1ab10b00d07d6e9dae8189722728) 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.