Which versions of time-webkit-tag are malicious?

The following npm versions of time-webkit-tag are flagged malicious: 20.1.6. Treat any of these as compromised.

How do I remediate time-webkit-tag if I installed it?

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.

I already installed time-webkit-tag — how do I know if it already compromised me?

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.

Is time-webkit-tag part of a known attack campaign?

Yes — time-webkit-tag is associated with the IN-MAL-2026-014617 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find time-webkit-tag across my projects, lockfiles, and CI pipelines?

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.

Malicious package

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)

MAL-2026-12226

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall time-webkit-tag

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.

Malicious versions

1 flagged

20.1.6

Indicators of compromise (SHA-256)

4da59763ac0349051b13656079486ab8c8c08971ff18c5efa84fbf8f5ce022a0

Detection & response playbook

Malicious package

Find 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

No. time-webkit-tag on npm has been identified as a malicious package (version 20.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014617

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database