Which versions of tslint-conf are malicious?

The following npm versions of tslint-conf are flagged malicious: 7.2.1. Treat any of these as compromised.

How do I remediate tslint-conf if I installed it?

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

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

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

Malicious package

tslint-confnpm

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

MAL-2026-7022

Immediate action

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

npm uninstall tslint-conf

What this malware does

The package presents itself as the pino logger (README, index.d.ts, docs/, and lib/ files all reference pinojs/pino) but is published under the unrelated name tslint-conf. Its default export is an Express-style middleware factory whose invocation synchronously calls runJobA, which uses child_process.spawn("node", ["lib/caller.js",...], { detached: true, stdio: "ignore" }) followed by child.unref() to launch a hidden background worker. lib/caller.js performs axios.get against https://peach-eligible-penguin-917.mypinata.cloud/ipfs/bafkreigjnxn5vnn34rc5r43ajwwkmk4akqpm4awmq5gdhakgszpeqiffsu, takes the response body, and passes it to new Function.constructor("require", s) then invokes the resulting function with require, granting the fetched code full Node.js capabilities on the host. The remote content is attacker-controlled (Pinata account under the operator's control), unpinned by hash/signature, and executed unconditionally on every use of the middleware. Combined with the pino cover story, any consumer misled into using this package as their logger triggers remote code execution.

Malicious versions

1 flagged

7.2.1

Indicators of compromise (SHA-256)

31b464b1646f8e2d36ce68a86af599cc49d5381f08af70302ff01f42957234a1

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

Campaign

IN-MAL-2026-008611

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tslint-conf-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