strapi-plugin-maylog-meebnpm
Advisory published Updated
strapi-plugin-maylog-meeb is a confirmed malicious npm package (MAL-2026-16233) that opens a backdoor for remote access (malicious version 3.6.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in strapi-plugin-maylog-meeb (npm)
What this malware does
The package's postinstall.js lifecycle script executes automatically on npm install and spawns a python3 reverse shell that connects to the hardcoded remote endpoint 14.225.210.85:80 and attaches an interactive sh PTY to the socket, giving the operator of that endpoint full shell access to the installer's host. Prior to the connect, the script collects host identifiers (os.hostname(), os.userInfo().username, process.pid) and writes them to /tmp/postinstall-revshell.log; those identifiers are also exposed to the remote endpoint once the shell attaches. The script retries on failure. The package name and description masquerade as a Strapi audit-log plugin; no functionality in the tarball corresponds to that stated purpose.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for strapi-plugin-maylog-meeb (version 3.6.8).
If you installed it — respond
strapi-plugin-maylog-meeb 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 strapi-plugin-maylog-meeb 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 strapi-plugin-maylog-meeb-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.