time-webkit-tagnpm
time-webkit-tag is a confirmed malicious npm package (MAL-2026-12226) that executes malicious code on install (malicious version 20.1.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in time-webkit-tag (npm)
What this malware does
On require of the package, index.js loads init.js which unconditionally invokes start(). start() selects a platform-specific asset path, assembles CDN hostnames from split string arrays (oob-worker.cf101-adf.workers.dev family, with a *.dl.well1.site DNS-TXT chunked-transfer fallback), fetches an opaque binary over HTTPS, writes it to /var/tmp or %TEMP% under a hidden dot-file or masquerading name (e.g..cache<rand>, dotnet_diag_<rand>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe with.unref(). No hash or signature verification is performed and the destination hosts are assembled at runtime to evade static string matching. A second dropper implementation in lib/telemetry.js repeats the same fetch/base64-decode/chmod/spawn chain, with the chmodSync and child_process identifiers built via string concatenation (fs["chmod"+"Sync"], "child_"+"process") under an analytics-SDK cover story. The package is advertised as a webkit tag provider and has no legitimate need for this behavior.
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
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for time-webkit-tag (version 20.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging time-webkit-tag across your stack and pipelines.
If you installed it — respond
Remove time-webkit-tag from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If time-webkit-tag 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 time-webkit-tag 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 time-webkit-tag-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.