claims-page-maker-typesnpm
claims-page-maker-types is a confirmed malicious npm package (MAL-2026-12630) that typosquats a legitimate package to trick installs (malicious version 35.5.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in claims-page-maker-types (npm)
What this malware does
On require() of claims-page-maker-types, index.js loads adapter.js which runs at module load. adapter.js selects a platform-specific asset, fetches an opaque binary over HTTPS from one of four hardcoded Cloudflare workers.dev hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS TXT fallback under wel1.ru (sdk.dl.wel1.ru), writes the payload to a disguised temp path (.cache<hex> on Unix, dotnet_diag<hex>.exe on Windows), chmods it 0755, and spawns it detached via /bin/sh -c or cmd. Host strings are assembled by Array.join from split fragments to evade plain-text scanners, filenames mimic system diagnostics, and a stamp file (analytics_state) throttles re-execution while comments frame the behavior as 'telemetry'. No pinning, no signature verification, and the destination hosts are not the package's registry or publisher infrastructure.
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 claims-page-maker-types (version 35.5.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging claims-page-maker-types across your stack and pipelines.
If you installed it — respond
claims-page-maker-types is a typosquat — you almost certainly intended a legitimately-named package. Remove claims-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 claims-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 claims-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 claims-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.