Which versions of caracas4check are malicious?

The following PyPI versions of caracas4check are flagged malicious: 1.1.1, 1.1.2. Treat any of these as compromised.

How do I remediate caracas4check if I installed it?

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

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

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

Malicious package

caracas4checkPyPI

caracas4check is a confirmed malicious PyPI package (MAL-2026-17198) that steals credentials and exfiltrates sensitive data (malicious versions 1.1.1, 1.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in caracas4check (PyPI)

MAL-2026-17198

Immediate action

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

pip uninstall caracas4check

What this malware does

During installation, the code downloads a malicious executable from a remote location. The malicious action is triggered only on specific hosts.

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

Campaign: 2026-09-caracas4check

Reasons (based on the campaign):

obfuscation
targetted-attack
Downloads and executes a remote executable.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

1.1.11.1.2

Indicators of compromise (SHA-256)

fe298eb267ef99191242315438fe8b7a619bece89e39d3e607cc34af455c647a

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

Campaign

2026-09-caracas4check

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database