Which versions of eslint-ts-view are malicious?

The following npm versions of eslint-ts-view are flagged malicious: 2.12.1. Treat any of these as compromised.

How do I remediate eslint-ts-view if I installed it?

Remove eslint-ts-view 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 eslint-ts-view — how do I know if it already compromised me?

If eslint-ts-view 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.

Is eslint-ts-view part of a known attack campaign?

Yes — eslint-ts-view is associated with the RLMA-2025-04515, RLUA-2025-05788 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 eslint-ts-view across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for eslint-ts-view (version 2.12.1).

Malicious package

eslint-ts-viewnpm

Advisory published Aug 28, 2025Updated Dec 2, 2025

eslint-ts-view is a confirmed malicious npm package (MAL-2025-41555) that executes malicious code on install (malicious version 2.12.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-ts-view (npm)

MAL-2025-41555

Immediate action

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

npm uninstall eslint-ts-view

Malicious versions

1 flagged

2.12.1

Indicators of compromise (SHA-256)

e333090b8e7f1da69e63c79a6a796bb995b98ff0902545533a79d8dcdb2ee381

f87c89979861c639a0b80ee8f8eada52bf60a18e137c4f6c1dce2df7896a942b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for eslint-ts-view (version 2.12.1).
If you installed it — respond
Remove eslint-ts-view 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 eslint-ts-view 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. eslint-ts-view on npm has been identified as a malicious package (version 2.12.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04515RLUA-2025-05788

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks eslint-ts-view-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