fry-page-maker-types (npm) · Malicious Code
Affects fry-page-maker-typesSource GCVE Database
Malicious package : remove fry-page-maker-types and rotate any secrets on hosts that installed it.
Data as of 6 Aug 2026, 18:24 UTC
Malicious package
Published to npm · OSV MAL-2026-12385
What to do
Remove fry-page-maker-types from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmfry-page-maker-types | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (aa133d7d2ce61c2b2b4d2c48beec5e819a49b52349f7f0b212e446a667457ea7) 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. ## Source: ghsa-malware (baa705869682cdd4f94383db6e54ff0d9043537865aeb128a6c75697379322f0) 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.