fry-page-maker-typesnpm
fry-page-maker-types is a confirmed malicious npm package (MAL-2026-12385) that typosquats a legitimate package to trick installs (malicious version 20.6.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in fry-page-maker-types (npm)
What this malware does
On require() of the package, index.js loads bootstrap.js, which selects a platform-specific payload (linux_x64, linux_arm64, darwin, win32), downloads it from Cloudflare Workers hosts whose names are reconstructed at runtime from split string fragments (e.g. oob-worker.cf100-416.workers.dev and sibling cf102-baf/cf103-070/cf99-9b3.workers.dev), with a DNS TXT-record covert-channel fallback via *.dl.well1.site. The fetched bytes are written to /var/tmp or %TEMP% under disguised names mimicking legitimate OS artifacts (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmodded 0755, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. A marker file.analytics_state is dropped alongside. Host names and endpoints are split-string obfuscated to evade static analysis. Simply importing this package as a library causes remote code execution on the installer's machine with the installer's privileges.
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 fry-page-maker-types (version 20.6.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fry-page-maker-types across your stack and pipelines.
If you installed it — respond
fry-page-maker-types is a typosquat — you almost certainly intended a legitimately-named package. Remove fry-page-maker-types, 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 fry-page-maker-types 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 fry-page-maker-types 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 fry-page-maker-types-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.