Which versions of xcepthttp are malicious?

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

How do I remediate xcepthttp if I installed it?

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

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

Yes — xcepthttp is associated with the RLMA-2025-02551, 2025-03-httpx-client, RLUA-2026-00936 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 xcepthttp 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 xcepthttp (version 0.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xcepthttp across your stack and pipelines.

Malicious package

xcepthttpPyPI

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

MAL-2025-3483

Immediate action

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

pip uninstall xcepthttp

What this malware does

Importing the module starts downloading and executing first a script, and then a widely identified malware

Packages are used as dependencies in a GitHub project https://github.com/ToolParadiseDrako/Nuker-Tool-Paradise

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

Campaign: 2025-03-httpx-client

Reasons (based on the campaign):

Downloads and executes a remote executable.
Downloads and executes a remote malicious script.
malware

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

d577682d10d3238d1a0873cb02d3fd1df050782f8430252d5e868543ad70ed20

dc2ee4745b16de4e91c6b2c51dd593552539cae654772b576e2d6a818fe51fe9

98504a58d8dccbb3ea09cc521e14c9a64707763302db04111ad32eeba8616925

1dd2ab026b74c200827ab1a7a93ecec97bdb7ce513d7b9e9787798581ef69c45

db5a810cb8fa16405ed0f867e62b5f87644360296c0dfde1dc3444499f2460e2

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

Campaign

RLMA-2025-025512025-03-httpx-clientRLUA-2026-00936

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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