Which versions of ts-lint-builds are malicious?

The following npm versions of ts-lint-builds are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate ts-lint-builds if I installed it?

ts-lint-builds is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed ts-lint-builds — how do I know if it already compromised me?

If ts-lint-builds 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 ts-lint-builds part of a known attack campaign?

Yes — ts-lint-builds is associated with the GHSA-rhr9-fqxc-vwqq 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 ts-lint-builds 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 ts-lint-builds (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-lint-builds across your stack and pipelines.

Malicious package

ts-lint-buildsnpm

ts-lint-builds is a confirmed malicious npm package (MAL-2026-2883) that steals credentials and exfiltrates sensitive data (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ts-lint-builds (npm)

MAL-2026-2883

Immediate action

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

npm uninstall ts-lint-builds

What this malware does

big.js typosquat campaign - SSH backdoor implantation, credential and crypto wallet theft

The package ts-lint-builds was found to contain malicious code.

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

1.0.5

Indicators of compromise (SHA-256)

1b5b6d9da5acae076b81860b7c119f9b61dd48b9b5360e56b582fdae563f96d8

f10fca1eb0f085174a194bd27deb1e579b9a904565a9142a390b244f9bea5410

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ts-lint-builds (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-lint-builds across your stack and pipelines.
If you installed it — respond
ts-lint-builds is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ts-lint-builds 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 ts-lint-builds 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. ts-lint-builds on npm has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rhr9-fqxc-vwqq

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks ts-lint-builds-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database