Which versions of carcent are malicious?

The following PyPI versions of carcent are flagged malicious: 2.1.0. Treat any of these as compromised.

How do I remediate carcent if I installed it?

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

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

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

Malicious package

carcentPyPI

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

MAL-2026-808

Immediate action

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

pip uninstall carcent

What this malware does

Package collects and exfiltrates Discord credentials from multiple sources

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

Campaign: 2025-06-soupclaw

Reasons (based on the campaign):

exfiltration-generic
exfiltration-env-variables
exfiltration-browser-data
exfiltration-credentials

Malicious versions

1 flagged

2.1.0

Indicators of compromise (SHA-256)

6672d1df7a6035da8ee0a2c7a4ed9e7e5bace551e5948fd2e7d7d31a18410a1c

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

Campaign

2025-06-soupclaw

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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