Which versions of sphinx-rdt-theme are malicious?

The following PyPI versions of sphinx-rdt-theme are flagged malicious: 95.6. Treat any of these as compromised.

How do I remediate sphinx-rdt-theme if I installed it?

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

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

Yes — sphinx-rdt-theme is associated with the 2024-11-byted-dast 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 sphinx-rdt-theme 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 sphinx-rdt-theme (version 95.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sphinx-rdt-theme across your stack and pipelines.

Malicious package

sphinx-rdt-themePyPI

Malicious code in sphinx-rdt-theme (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10730

Immediate action

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

pip uninstall sphinx-rdt-theme

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'sphinx-rdt-theme' @ 95.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

95.6

Indicators of compromise (SHA-256)

7529df75411c1ed03b1d6c6b9c32753ab63b06d5a550abbce5d1a0517a60d87d

abc5503cfe3fe246777ea2ed0c001bdb776e9ca5f6c0aa95d2c12c60e9458b5f

8397635bb7a7130efa3b0f3b924fbb3b61c66ab82baedef14452ded787f4e00a

3414740c1be07bb7857441db29866fb9b1c9b38f1d559a11817c824f94f6bc9a

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

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks sphinx-rdt-theme-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