sysnodenpm
Advisory published Updated
sysnode is a confirmed malicious npm package (MAL-2026-4678) that steals credentials and exfiltrates sensitive data (malicious version 1.0.25). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sysnode (npm)
What this malware does
Package self-describes as a 'System binary configuration tool' but on invocation (CLI/bin entry or require) it silently bootstraps a full surveillance stack on Windows. index.js:42-47 uses winget and, as fallback, curls https://www.python.org/ftp/python/3.12.3/python-3.12.3-amd64.exe to %TEMP% and runs the installer with /quiet InstallAllUsers=0 PrependPath=1 to avoid UAC and any visible UI. It then pip-installs keyboard, pyperclip, mss, pyautogui, uiautomation, and comtypes — the canonical keylogger / clipboard-scrape / screen-capture / UI-automation library set — and spawns a pyarmor 9.2.4 trial-encrypted pointer.py (loaded via pyarmor_runtime_000000.__pyarmor__ from a 624 KB native.pyd) with shell:false and a comment explicitly noting the goal of running without a CMD window. The actual capture/exfil logic is hidden inside the pyarmor blob and cannot be reviewed. The package's stated purpose, generic keywords, and placeholder author 'ABC' do not match observed behavior — a cover story for a Windows surveillance dropper.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for sysnode (version 1.0.25).
If you installed it — respond
sysnode 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 sysnode 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks sysnode-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.