time-linters-webapp-eslint-confignpm
time-linters-webapp-eslint-config is a confirmed malicious npm package (MAL-2026-12479) that executes malicious code on install (malicious version 20.2.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in time-linters-webapp-eslint-config (npm)
What this malware does
The package's top-level index.js unconditionally requires./runtime on load. runtime.js assembles a rotating list of Cloudflare Workers hostnames (oob-worker.cf100/101/102/103-*.workers.dev) and a *.dl.well1.site DNS-TXT fallback via array-join string splits to evade static analysis, downloads a platform-specific binary over https.get, writes it to a temp path using cover-story filenames (.cache<rand>, dotnet_diag<rand>.exe,.analytics_state), chmods it 0755 on POSIX, and spawns it detached via spawn("/bin/sh", ["-c", fp + " &"]) or spawn("cmd",...) on Windows. No hash or signature verification is performed, the fetched bytes are opaque, and the destinations have no relationship to any ESLint configuration purpose. A fake telemetry framing (DISABLE_TELEMETRY / DO_NOT_TRACK opt-outs,.analytics_state cache) is used as cover. Fires on any require()/import of the package, including transitively.
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-linters-webapp-eslint-config (version 20.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging time-linters-webapp-eslint-config across your stack and pipelines.
If you installed it — respond
Remove time-linters-webapp-eslint-config 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-linters-webapp-eslint-config 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-linters-webapp-eslint-config 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-linters-webapp-eslint-config-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.