web-vitals-polyfill-core-v1npm
web-vitals-polyfill-core-v1 is a confirmed malicious npm package (MAL-2026-17303) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in web-vitals-polyfill-core-v1 (npm)
What this malware does
The package name mimics the widely-used web-vitals polyfill but the tarball ships disk/index.min.js, a base64-wrapped service-worker payload (self.PWA_ROUTER.executeTacticalRouting) that resolves an active destination via DoH TXT lookups of api.chinazhangsan.ccwu.cc (queried through doh.pub and dns.alidns.com) with base64-encoded fallback endpoints on gist.githubusercontent.com/chinazhangsan999-crypto and api.npoint.io, performs decoy fetches, and issues Response.redirect(targetUrl, 302) to the resolved host. package.json declares main: index.js which is not present in the tarball, so the package has no legitimate library surface; its shipped code is exclusively the obfuscated redirector, intended to be loaded into a consuming site's service worker where it can hijack end-user navigation to attacker-chosen destinations resolved at runtime through multi-provider DNS-over-HTTPS and paste-site fallbacks.
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 web-vitals-polyfill-core-v1 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging web-vitals-polyfill-core-v1 across your stack and pipelines.
If you installed it — respond
web-vitals-polyfill-core-v1 is a typosquat — you almost certainly intended a legitimately-named package. Remove web-vitals-polyfill-core-v1, 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 web-vitals-polyfill-core-v1 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 web-vitals-polyfill-core-v1 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 web-vitals-polyfill-core-v1-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.