Which versions of tsesyx are malicious?

The following PyPI versions of tsesyx are flagged malicious: 10.0.5. Treat any of these as compromised.

How do I remediate tsesyx if I installed it?

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

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

Yes — tsesyx is associated with the RLMA-2025-04288, 2025-07-triple-equals, RLUA-2026-00867 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 tsesyx 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 tsesyx (version 10.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tsesyx across your stack and pipelines.

Malicious package

tsesyxPyPI

Malicious code in tsesyx (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-41790

Immediate action

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

pip uninstall tsesyx

What this malware does

When imported, the package attempts to exfiltrate environment variables and basic user info

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-07-triple-equals

Reasons (based on the campaign):

exfiltration-env-variables
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

10.0.5

Indicators of compromise (SHA-256)

980a9a77c128d2ed5a54b014dc0080c745e74f7d3aba31ad4542585a71244cae

884383ef26c14f8a606374b70c24361b5cdf26da20b5723e55c824c85d49770b

7c8ea2b8c69693d4bd40c7c4b952878565e3bfaa6eb0ea02ab6ef9ca18eadea8

79c93ef0d721adb368d09b9fb1e00653d06458626bc90f5cf8d911e189373c74

0a895274ce3ed743ecd4e5179cccaac6a54498d7109e91eed109ead5ff92587d

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

Campaign

RLMA-2025-042882025-07-triple-equalsRLUA-2026-00867

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks tsesyx-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