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

strapi-plugin-persh-meebnpm

strapi-plugin-persh-meeb is a confirmed malicious npm package (MAL-2026-16237) that executes malicious code on install (malicious version 3.6.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in strapi-plugin-persh-meeb (npm)

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

What this malware does

[email protected] ships a postinstall.js (also declared as the package main) that runs automatically on npm install. The script spawns a Python one-liner that opens a TCP socket to the hardcoded bare IP 14.225.210.85 on port 443 (with:80 also referenced), duplicates the socket over stdio, and calls pty.spawn("sh"), giving the remote host an interactive shell on the installer's machine. Retries up to 5 times at 10-second intervals. Execution is gated by a hostname allowlist check (os.hostname() === 'ubuntu-fc-uvm') and logs to /tmp/postinstall-revshell.log, consistent with a targeted red-team or victim-tuned implant. The destination is a bare IP unrelated to any Strapi or plugin-publisher infrastructure, and the package name resembles the Strapi plugin ecosystem.

Malicious versions

1 flagged
3.6.8

Indicators of compromise (SHA-256)

67ce68eeb9a309b5fff512e24a1b8f4c12fb171c0752d6a04293a4e72c805088

Detection & response playbook

Malicious package
  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-persh-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-persh-meeb across your stack and pipelines.

  2. If you installed it — respond

    Remove strapi-plugin-persh-meeb from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If strapi-plugin-persh-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-persh-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-persh-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-020101

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks strapi-plugin-persh-meeb-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

strapi-plugin-persh-meeb (npm) malicious package — MAL-2026-16237 | O3 Security