me5123npm
Advisory published Updated
me5123 is a confirmed malicious npm package (MAL-2026-20048) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in me5123 (npm)
What this malware does
Malicious package. An install script runs node index.js, which executes hostname, whoami, hostname -I and date and posts the results to a Telegram bot (api.telegram.org). Observed in a sandboxed install. index.js (sha256 fba01e6f8d33065d3cbf549eaece41c5c28fbf0f54ef833cab3c4ce555cd2c93) is identical to the file in @0xme5war/apicli (MAL-2025-6684) and inditextech (MAL-2025-6349). Published 2025-07-28 and unpublished from npm within an hour.
Malicious versions
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for me5123 (version 1.0.0).
If you installed it — respond
me5123 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 me5123 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
References
Credits
- wormsign · finder
Detect & block this
O3 blocks me5123-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.