Which versions of singtok are malicious?

The following PyPI versions of singtok are flagged malicious: 0.0.1, 0.0.3, 0.0.4. Treat any of these as compromised.

How do I remediate singtok if I installed it?

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

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

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

Malicious package

singtokPyPI

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

MAL-2025-191868

Immediate action

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

pip uninstall singtok

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

3 flagged

0.0.10.0.30.0.4

Indicators of compromise (SHA-256)

3334e722f7b75e431c3c41f9daaf95f192a005354093f7fb4d7b0edae8d613c0

20dad294eb5c742d0044f1dde01f51646f0b34a86a7cb86c84547981276f46ce

d4549fba2358242661530a53506fbd15808f05271ae18b1b1a296f6ceecdd30f

94f31de9f6e4db4aac73ff160fac8e40c47cf5f333f26aa37fb2a7278911a154

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 singtok (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging singtok across your stack and pipelines.
If you installed it — respond
singtok 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 singtok 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 singtok 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. singtok on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.3, 0.0.4 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 singtok-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