Which versions of tiksing are malicious?

The following PyPI versions of tiksing are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate tiksing if I installed it?

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

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

Yes — tiksing is associated with the 2025-02-tiksing 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 tiksing 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 tiksing (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tiksing across your stack and pipelines.

Malicious package

tiksingPyPI

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

MAL-2025-191899

Immediate action

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

pip uninstall tiksing

What this malware does

Importing the module starts Obfuscated code that downloads a well-recognized malware. In the further variations, the code that download and starts the malicious code is now a little more hidden in the functionality and starts after presenting some allegedly expected activity

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

Campaign: 2025-02-tiksing

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
malware

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

3ea76770bdbedf8c54236f3a10f324a15b48c3fe41e42fa60bf82fe8199f496f

ef883e1ad19e5cbeafdda023c535abc9a14f84f81dce26e06d9f10bf77013ab5

ec4bc55e32edab7c31f502f53ae8c5898c5252751182fb43906548e8faf6d9d2

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

Campaign

2025-02-tiksing

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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