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

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

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

strapi-plugin-weccresh-meeb is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

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

Malicious package

strapi-plugin-weccresh-meebnpm

strapi-plugin-weccresh-meeb is a confirmed malicious npm package (MAL-2026-16192) that steals credentials and exfiltrates sensitive data (malicious version 3.6.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in strapi-plugin-weccresh-meeb (npm)

MAL-2026-16192

Immediate action

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

npm uninstall strapi-plugin-weccresh-meeb

What this malware does

The package's postinstall.js (also declared as main) executes automatically on npm install and performs bulk host reconnaissance and credential theft against the installer. It captures os.hostname() and os.userInfo(), serializes the full process.env, reads Strapi configuration under /app/config/* and /app/.env*, recursively walks the filesystem from '/' to collect files matching.env* and private-key/certificate patterns (pem, key, crt, cert, p12, pfx, jks, id_rsa, wallet), reads Kubernetes service-account tokens under /var/run/secrets/kubernetes.io/serviceaccount/token and /run/secrets, probes /var/run/docker.sock, reads /etc/hosts and /etc/resolv.conf, and queries Redis INFO/DBSIZE and database table counts via knex. The collected data is gzip-compressed, base64-encoded, split into 3500-byte chunks, and POSTed with staggered timeouts to the hardcoded Burp Collaborator host q0r2hkrfha7y7zhz6nxtqqifv61xppde.oastify.com on port 80. The package name mimics a Strapi plugin but ships no plugin code; the postinstall exfiltration is the only behavior.

Malicious versions

1 flagged

3.6.8

Indicators of compromise (SHA-256)

4b4a6e3de6177f265d44cf7317b020dbaed43907a0ed75b05ae0fe4eebaab469

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for strapi-plugin-weccresh-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-weccresh-meeb across your stack and pipelines.
If you installed it — respond
strapi-plugin-weccresh-meeb is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If strapi-plugin-weccresh-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-weccresh-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-weccresh-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-020064

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks strapi-plugin-weccresh-meeb-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database