Which versions of tslint-slick are malicious?

The following npm versions of tslint-slick are flagged malicious: 5.0.0, 5.0.2, 5.0.3. Treat any of these as compromised.

How do I remediate tslint-slick if I installed it?

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

If tslint-slick 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 tslint-slick part of a known attack campaign?

Yes — tslint-slick is associated with the GHSA-v64f-52wj-8w22, RLMA-2024-02002 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 tslint-slick 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 tslint-slick (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tslint-slick across your stack and pipelines.

Malicious package

tslint-slicknpm

tslint-slick is a confirmed malicious npm package (MAL-2024-1127) that executes malicious code on install (malicious versions 5.0.0, 5.0.2, 5.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tslint-slick (npm)

MAL-2024-1127

Immediate action

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

npm uninstall tslint-slick

What this malware does

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

3 flagged

5.0.05.0.25.0.3

Indicators of compromise (SHA-256)

a2759b172d96a68a7783fab890e408535923abfd9ef8760d01d1e9f12f7dd0ad

ca5ba4d2d6b429ef7b0669ee27285c778a5614c7ad9cc7851d91e5549a0d2dfc

d797a6b1d9b0c5a10084e696d9f03897fc8559e0792dffa8e7414d37629c9b2a

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 tslint-slick (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tslint-slick across your stack and pipelines.
If you installed it — respond
Remove tslint-slick 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 tslint-slick 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 tslint-slick 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. tslint-slick on npm has been identified as a malicious package (versions 5.0.0, 5.0.2, 5.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-v64f-52wj-8w22RLMA-2024-02002

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks tslint-slick-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