fetch-page-assetsnpm
fetch-page-assets is a confirmed malicious npm package (MAL-2026-6358) that opens a backdoor for remote access (malicious versions 1.2.9, 1.2.10, 1.2.11…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in fetch-page-assets (npm)
What this malware does
babel.config.cjs contains a heavily obfuscated (obfuscator.io-style) IIFE appended after a legitimate @babel/preset-env block. It queries multiple Ethereum RPC endpoints (1rpc.io/eth, eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blastapi.io, eth.blockscout.com/api) for transactions from the on-chain address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, decodes two IPv4 C2 addresses from the transaction's destination field, fetches XOR-encrypted stage-2 payloads from those hosts at /0x/cls and /0x/ls, decrypts them with hardcoded keys, and executes the result via both eval and spawn('node', ['-e', payload], {detached:true, stdio:'ignore', windowsHide:true}).unref(). A second copy of the same dropper is smuggled as public/fonts/fa-solid-400.woff2 — the file is not a font but plain JS beginning with global.i="A8-*#";global.r=require; and requiring http/https/zlib/child_process, with identical on-chain address, endpoints, and XOR keys. Requires of child_process, http, https, zlib, and url are Unicode-escaped to evade static inspection. Any consumer that installs this package and runs a Babel-using workflow (jest, build, transpile) executes attacker-controlled remote code whose current location is dynamically resolved from the Ethereum blockchain, giving the operator resilient, takedown-resistant C2 on the installer's machine.
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
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fetch-page-assets (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fetch-page-assets across your stack and pipelines.
If you installed it — respond
fetch-page-assets 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 fetch-page-assets 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 fetch-page-assets 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 fetch-page-assets-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.