fs-extra-corenpm
fs-extra-core is a confirmed malicious npm package (MAL-2026-11027) that typosquats a legitimate package to trick installs (malicious version 1.3.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in fs-extra-core (npm)
What this malware does
Package impersonates fs-extra by copying its description, homepage (github.com/jprichardson/node-fs-extra), and repository metadata verbatim. Its exported outputFile() function ignores the documented (path, data) arguments and instead fetches a Windows executable from raw.githubusercontent.com/jason-code-super/axios/main/lib/env/axios.exe — a personal repository unrelated to the fs-extra publisher — and writes the binary to %LOCALAPPDATA%\Temp\msedgewebview2.exe, a filename impersonating Microsoft Edge WebView. Any consumer calling the fs-extra-style outputFile API stages an attacker-controlled binary on disk under a Microsoft-lookalike name, sourced from a mutable third-party GitHub branch.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fs-extra-core (version 1.3.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fs-extra-core across your stack and pipelines.
If you installed it — respond
fs-extra-core is a typosquat — you almost certainly intended a legitimately-named package. Remove fs-extra-core, 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 fs-extra-core 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 fs-extra-core 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks fs-extra-core-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.