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

strapi-plugin-conresh-meebnpm

strapi-plugin-conresh-meeb is a confirmed malicious npm package (MAL-2026-16229) that typosquats a legitimate package to trick installs (malicious version 3.6.8). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

What this malware does

The package declares a postinstall lifecycle hook ("postinstall": "node postinstall.js") that executes on every npm install. postinstall.js invokes child_process.exec with a bash reverse-shell command connecting the installer's host to the hardcoded remote endpoint 14.225.210.85:80 via /dev/tcp, redirecting stdio to give the remote party an interactive shell on the installer's machine. Execution is gated by a hostname allowlist (matching 'ubuntu-fc-uvm'), and a retry loop plus a log file at /tmp/postinstall-revshell.log indicate a persistent, targeted deployment. The plugin name mimics the Strapi plugin namespace but ships no plugin functionality relevant to that framing.

Malicious versions

1 flagged
3.6.8

Indicators of compromise (SHA-256)

d117fca143f7c8f02261755b923b29cae47f8fdcca2f69f169e26a5601b3661a

Detection & response playbook

Typosquat
  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-conresh-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-conresh-meeb across your stack and pipelines.

  2. If you installed it — respond

    strapi-plugin-conresh-meeb is a typosquat — you almost certainly intended a legitimately-named package. Remove strapi-plugin-conresh-meeb, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If strapi-plugin-conresh-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-conresh-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-conresh-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-020096

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks strapi-plugin-conresh-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-conresh-meeb (npm) malicious package — MAL-2026-16229 | O3 Security