If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (c82adb424b76ab7db887024cb8608a8e7aa3b942797ba38a3eef74fa36c249e5)
The package's postinstall hook (callback.js) and its declared main entry (index.js, byte-identical to callback.js) both write a Python script to /tmp/attack.py and spawn it via `nohup python3 /tmp/attack.py... &`. The script launches hundreds of UDP/TCP flood threads against the hardcoded target 103.118.252.21 for 600 seconds, turning the installer's host into a DDoS source against a third party. After launching the flood, the code collects host identifiers (`id`, `hostname`, running process count, /proc/loadavg), base64-encodes them, and issues an HTTPS GET to jasabersama.id/portfolio-data.php with query parameters `k=S7k9xQ2mZj&c=<base64>`, with TLS certificate verification disabled (`rejectUnauthorized: false`). Because index.js is the module's main entry, the same dropper also fires whenever the package is `require`d — for example when loaded as an n8n community node — in addition to firing on `npm install` via the postinstall lifecycle hook.