Which versions of strapi-plugin-maylog-meeb are malicious?

The following npm versions of strapi-plugin-maylog-meeb are flagged malicious: 3.6.8. Treat any of these as compromised.

How do I remediate strapi-plugin-maylog-meeb if I installed it?

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.

I already installed strapi-plugin-maylog-meeb — how do I know if it already compromised me?

If strapi-plugin-maylog-meeb was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is strapi-plugin-maylog-meeb part of a known attack campaign?

Yes — strapi-plugin-maylog-meeb is associated with the IN-MAL-2026-020093 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find strapi-plugin-maylog-meeb across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for strapi-plugin-maylog-meeb (version 3.6.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging strapi-plugin-maylog-meeb across your stack and pipelines.

Malicious package

strapi-plugin-maylog-meebnpm

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)

MAL-2026-16233

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall strapi-plugin-maylog-meeb

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

1 flagged

3.6.8

Indicators of compromise (SHA-256)

8d714c1585f058d5ac528832398ffe2d0035fd8b60e97e461cdfa8e1533e851c

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for strapi-plugin-maylog-meeb (version 3.6.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging strapi-plugin-maylog-meeb across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks strapi-plugin-maylog-meeb before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. strapi-plugin-maylog-meeb on npm has been identified as a malicious package (version 3.6.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020093

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database