Which versions of tsconfig-slick are malicious?

The following npm versions of tsconfig-slick are flagged malicious: 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.7.0. Treat any of these as compromised.

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

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

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

Yes — tsconfig-slick is associated with the GHSA-ccmf-pmvq-f432, RLMA-2024-02001 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 tsconfig-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 tsconfig-slick (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tsconfig-slick across your stack and pipelines.

Malicious package

tsconfig-slicknpm

tsconfig-slick is a confirmed malicious npm package (MAL-2024-1126) that executes malicious code on install (malicious versions 3.0.1, 3.0.2, 3.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tsconfig-slick (npm)

MAL-2024-1126

Immediate action

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

npm uninstall tsconfig-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

5 flagged

3.0.13.0.23.0.33.0.43.7.0

Indicators of compromise (SHA-256)

feb6f5d0d440575be958acf30cdad5674315b1be245f2459de868d74f09516ed

4feaf97765df26df82e01804cb4cd6d43f90a2c4c2f7ff480c3cc0346bdf16a5

83981ac0c9860da6b4943b7c5febb30d186e0dcec1259dc976e4fbabf8c91814

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

Campaign

GHSA-ccmf-pmvq-f432RLMA-2024-02001

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks tsconfig-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