Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

strapi-plugin-perev-meebnpm

strapi-plugin-perev-meeb is a confirmed malicious npm package (MAL-2026-16236) 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-perev-meeb (npm)

MAL-2026-16236
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall strapi-plugin-perev-meeb

What this malware does

The npm postinstall hook executes postinstall.js, which uses child_process to spawn a Python reverse shell that connects to the hardcoded remote host 14.225.210.85:80 and dup2's a PTY-backed /bin/sh over the socket, giving the operator of that host an interactive shell on the installer's machine. Execution is gated by a hostname allowlist check (os.hostname() === 'ubuntu-fc-uvm'), a target-restriction technique that keeps the payload dormant on unintended hosts (scanners, sandboxes) and only detonates on the intended victim. The package presents itself as a Strapi plugin but ships no plugin functionality relevant to the postinstall behavior; the postinstall is the payload.

Malicious versions

1 flagged
3.6.8

Indicators of compromise (SHA-256)

29840a9eddc4894177d910b38ef1808c0ba7a402c267160fe8e86cff48873700

Detection & response playbook

Backdoor / remote access
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for strapi-plugin-perev-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-perev-meeb across your stack and pipelines.

  2. If you installed it — respond

    strapi-plugin-perev-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.

  3. Did it already run?

    If strapi-plugin-perev-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.

  4. How O3 protects you

    O3 blocks strapi-plugin-perev-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-perev-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-020099

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks strapi-plugin-perev-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.

Explore

strapi-plugin-perev-meeb (npm) malicious package — MAL-2026-16236 | O3 Security