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

strapi-plugin-ccrec-meebnpm

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

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

What this malware does

The package's postinstall lifecycle script (postinstall.js) executes a bash /dev/tcp reverse shell to the hardcoded remote endpoint 14.225.210.85:80, giving the operator of that host an interactive shell on the installer's machine. Execution is gated by an os.hostname() equality check against 'ubuntu-fc-uvm'; on a matching host the script retries the connection up to 5 times, and on any other host it exits silently. The hostname gate is an evasion mechanism that hides the payload from generic installers and sandboxes while enabling targeted exploitation. The behavior fires automatically on npm install via scripts.postinstall with no user interaction. The package name mimics a Strapi plugin but ships no plugin functionality consistent with the declared purpose.

Malicious versions

1 flagged
3.6.8

Indicators of compromise (SHA-256)

27dd1178f43debcd9babc6630aa303b6953e7572d994f8efe3acc75db2cc878e

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

  2. If you installed it — respond

    strapi-plugin-ccrec-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-ccrec-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-ccrec-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-ccrec-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-020103

References

Credits

  • Amazon Inspector · finder

Detect & block this

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