node-helpernpm

The package impersonates the legitimate blakeembrey/node-helper library (matching author metadata, README, MIT license, and top-of-file helper functions) but appends a heavily obfuscated IIFE (obfuscator.io-style rotated string array with base64+URI decoder) that runs at require() time. The IIFE creates a hidden directory under os.homedir(), writes a second-stage obfuscated index.js and a synthesized package.json declaring dependencies axios, better-sqlite3, node-machine-id, socket.io-client, and on Windows @primno/dpapi and node-window-manager, then spawns npm install in that directory and launches the dropped payload detached. On win32 it additionally writes a main.vbs wrapper that uses WScript.Shell to Run the node payload hidden and non-waiting, and invokes C:\Windows\system32\wscript.exe against it with detached:true, windowsHide:true, and stdio ignored to keep the process alive after the installer exits. The Windows dependency combination (@primno/dpapi + better-sqlite3 + node-machine-id + node-window-manager + socket.io-client) is the standard toolkit for decrypting and exfiltrating Chrome/Edge Login Data and Cookies SQLite stores via DPAPI. The manifest also self-references node-helper: ^1.5.4, and the resolved second-stage code is whatever the attacker-controlled dependency graph delivers at install time.

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.