Which versions of ts-elinter are malicious?

The following npm versions of ts-elinter are flagged malicious: 3.3.9. Treat any of these as compromised.

How do I remediate ts-elinter if I installed it?

ts-elinter is a typosquat — you almost certainly intended a legitimately-named package. Remove ts-elinter, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — ts-elinter is associated with the IN-MAL-2026-007879 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-elinter 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-elinter (version 3.3.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-elinter across your stack and pipelines.

Malicious package

ts-elinternpm

Malicious code in ts-elinter (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6720

Immediate action

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

npm uninstall ts-elinter

What this malware does

On npm install, the package's postinstall script (scripts/install-check.cjs) fetches a JSON pointer from https://trabalhos-flax.vercel.app/config/clob-math.json, downloads the referenced.tgz to a temp directory, extracts it, runs npm install inside the extracted bundle, then require()s peer-math.js and invokes syncSession(). The remote source is a mutable third-party Vercel host with no pinning, no hash verification, and no signature check — whatever content the endpoint currently serves executes as Node on the installer's machine. The package name ts-elinter and description 'Teypscrip linkter for termnical' impersonate TypeScript/ESLint tooling, while the actual exported API is unrelated Polymarket Kelly-stake helpers. Cover-story naming (peer-math.js, syncSession, PSM_PEER_URL, log tag [polymarket-stake-math]) frames the loader as a benign peer-dependency sync.

Malicious versions

1 flagged

3.3.9

Indicators of compromise (SHA-256)

ce2fcb236f368214aa75fe60d233081a72077737e856e403c15d44fe9c940767

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ts-elinter (version 3.3.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-elinter across your stack and pipelines.
If you installed it — respond
ts-elinter is a typosquat — you almost certainly intended a legitimately-named package. Remove ts-elinter, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If ts-elinter 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-elinter 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-elinter on npm has been identified as a malicious package (version 3.3.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007879

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ts-elinter-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