Critical Malicious Code Vulnerability in ts-lint-builder Package

ts-lint-builder Updated 13 Mar 2026

Summary

11/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1346: Malicious code in ts-lint-builder (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The ts-lint-builder package is a tool used in the JavaScript ecosystem, specifically for linting TypeScript code. It helps developers maintain code quality by identifying potential errors and enforcing coding standards. However, this package has been compromised, leading to severe security risks for any system that has it installed.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the ts-lint-builder package. This code can fully compromise any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this malicious code is linked to a known malware source, and it poses a significant threat to system integrity and data security.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ts-lint-builder

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There are no effective workarounds for this vulnerability other than removing the package entirely. Ensure that you have rotated any sensitive information that may have been exposed.

Conclusion

The ts-lint-builder package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any sensitive information that may have been compromised. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for ts-lint-builder →

Share this vulnerability

FAQ

ts-lint-builder is a tool used for linting TypeScript code, helping developers maintain code quality and adhere to coding standards.

If you have the ts-lint-builder package installed, your system is potentially compromised. It is advisable to remove the package and check for any unauthorized access to sensitive information.

Immediately rotate all secrets and keys stored on the compromised system from a different, secure computer to prevent unauthorized access.

Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ts-lint-builder

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback