Which versions of m3fdfocdoewn are malicious?

The following npm versions of m3fdfocdoewn are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate m3fdfocdoewn if I installed it?

m3fdfocdoewn is a typosquat — you almost certainly intended a legitimately-named package. Remove m3fdfocdoewn, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed m3fdfocdoewn — how do I know if it already compromised me?

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

Yes — m3fdfocdoewn is associated with the IN-MAL-2026-019280 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 m3fdfocdoewn 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 m3fdfocdoewn (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging m3fdfocdoewn across your stack and pipelines.

Malicious package

m3fdfocdoewnnpm

m3fdfocdoewn is a confirmed malicious npm package (MAL-2026-15606) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in m3fdfocdoewn (npm)

MAL-2026-15606

Immediate action

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

npm uninstall m3fdfocdoewn

What this malware does

Published as part of a ClickFix-style fake-CAPTCHA phishing campaign documented by OX Security (see reference). The package's only file is index.html, declared as the npm "main" entry; package.json defines no preinstall/install/postinstall/prepare lifecycle script, so the payload does not execute at npm install time. index.html renders a fake Cloudflare Turnstile verification widget. An obfuscator.io-obfuscated inline script builds a hardcoded redirect URL to https://login.microsofte.live/ (a typosquat of a Microsoft sign-in domain), appends the visitor's original query-string parameters, and navigates the browser there via window.location.replace(). The package therefore does not attack the installing machine directly; it is used as a static file host on the npm CDN (e.g. unpkg/jsDelivr) so the index.html can be linked to and opened directly in a victim's browser as a phishing/ClickFix landing page. Published by npm user "johnvaldez9a" as part of a burst of near-identical single-purpose packages published between 2026-08-04 and 2026-08-24 that share this same fake-Turnstile-redirect page structure.

The package was found to contain malicious code or consuming dependency that contains malicious code

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5eacbd727bafd64bdcda408fb10b13d4a88c02614922d028a6404c6f372cb5fd

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for m3fdfocdoewn (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging m3fdfocdoewn across your stack and pipelines.
If you installed it — respond
m3fdfocdoewn is a typosquat — you almost certainly intended a legitimately-named package. Remove m3fdfocdoewn, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If m3fdfocdoewn 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 m3fdfocdoewn 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. m3fdfocdoewn on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019280

References

Credits

Amazon Inspector · finder
OX Security · finder

Detect & block this

O3 blocks m3fdfocdoewn-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database