Which versions of siitoogether are malicious?

The following PyPI versions of siitoogether are flagged malicious: 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9. Treat any of these as compromised.

How do I remediate siitoogether if I installed it?

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

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

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

Malicious package

siitoogetherPyPI

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

MAL-2025-191867

Immediate action

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

pip uninstall siitoogether

What this malware does

Importing the module starts an RAT-like process capable of execute remote commands, with the C2 through Discord

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

Campaign: 2025-11-siitoogether

Reasons (based on the campaign):

rat
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

Malicious versions

5 flagged

0.0.50.0.60.0.70.0.80.0.9

Indicators of compromise (SHA-256)

1f07b41d83d714a90622c9abc22affc518176086a25b1ee1a5563ddf3019d510

6fccd687f1acb55e6da0782b08ef14b3e8be5587dee4743a163a106c48390a50

e0b5bcc46e90b8aa200aff83c713b9f6afb53d010d4043e5c88a1c22d5031272

1da154e840e1a79623029e4feba610455f0ad78857de6bfbc5b4f335386b4f38

e6f8abb4071014fb37ccec1eae6a202c348c1e7195a9e248c755f15ca9ee0346

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

Campaign

2025-11-siitoogetherRLMA-2025-06591RLUA-2026-00758

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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