ts-eslinter
This report shows the evidence for ts-eslinter@1.0.0, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-6896 confirms this npm version as malicious.
Advisory
MAL-2026-6896
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in ts-eslinter (npm)
Details
Package name resembles common ESLint/TypeScript tooling and the main entry index.js contains base64 decoding via Buffer.from(..., 'base64').toString('utf8') at line 7 (with another Buffer.from at line 86). Base64 decoding of an embedded string is a common precursor to obfuscated payload execution, but it is also used for many legitimate purposes (config blobs, asset embedding, default keys). Without traced execution showing the decoded bytes being eval'd, executed via child_process, or sent over the network, intent cannot be confirmed from the available evidence. The name is also close to legitimate linter packages, which warrants a human look.
## Source: ghsa-malware (a31a70f73d25ed15fda28427e476afffbf8c8c5a617b9afb8c5d1b76d11d9154) 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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to ts-eslinter@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing ts-eslinter@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.