NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

time-linters-webapp-eslint-confignpm

Advisory published Updated

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)

MAL-2026-12479
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall time-linters-webapp-eslint-config

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

1 flagged
20.2.2

Indicators of compromise (SHA-256)

2b89eb401bae118699fcd79b686c0d6ace5e579df1ea42a87d6ad18de405614c
9edaeb4505249430e8e683569222e89185679cc9ce47210de6cca5d8a1df4a25

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for time-linters-webapp-eslint-config (version 20.2.2).

  2. 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.

  3. Did it already run?

    If time-linters-webapp-eslint-config was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-014693GHSA-xm67-8mvr-77j7

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.

Explore

time-linters-webapp-eslint-config (npm) malicious package — MAL-2026-12479 | O3 Security