strapi-plugin-listcc-meebnpm
Advisory published Updated
strapi-plugin-listcc-meeb is a confirmed malicious npm package (MAL-2026-16232) 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-listcc-meeb (npm)
What this malware does
[email protected] declares scripts.postinstall = 'node postinstall.js' (and points main at the same file), so npm install auto-executes postinstall.js. That script spawns a Python one-liner via child_process that opens a socket to the hardcoded IP 14.225.210.85:80 and attaches a PTY-backed /bin/sh to the remote peer, yielding an interactive reverse shell on the installer's host. Execution is gated only by a hostname check ('ubuntu-fc-uvm'). Package metadata masquerades as a Strapi plugin ('Strapi plugin for enhanced functionality') while the repository/homepage is a placeholder github.com/user/... URL and the shipped code contains no plugin functionality — only the reverse-shell payload.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for strapi-plugin-listcc-meeb (version 3.6.8).
If you installed it — respond
strapi-plugin-listcc-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-listcc-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-listcc-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.