NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

caracas4checkPyPI

Advisory published Updated

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

The package installs boot.pth at the site-packages root, causing 'import c4c_boot' to run on every Python interpreter startup on the host after installation, not only at install time. c4c_boot.py walks up to 8 parent processes via /proc/<pid>/stat and reads /proc/<pid>/cmdline to extract '--extra-index-url=' argument values from the invoking pip/CI process. Each recovered URL value is hashed (sha256(value+'gate')) and compared against a hardcoded allow-list _H of target hashes; on match, the URL string is used as an XOR key to decrypt one of two hex-encoded blobs in _B, and if the plaintext begins with 'OK\n' the remainder is passed to exec() with the URL bound as variable T. The plaintext payload is not recoverable without knowing the exact private index URL of the targeted organization. The README documents installation of an internal package named 'python3/caracas4check' from a private GitLab PyPI index via '--extra-index-url', and this public PyPI package of the same name ships only the.pth bootstrap plus the URL-gated decrypt-and-exec loader — the canonical dependency-confusion delivery shape, with anti-analysis obfuscation (URL-derived XOR key, hash-gated detonation) that only fires for the intended victim.

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
973d711f03dafa9f390e489476d4795acdda8db926bdd688ca5e1abbe6efa025
d4e20377146c9380ef7e3232f966f33507c41e79471fbda3b514c571e35145d1

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for caracas4check (2 malicious versions).

  2. 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.

  3. Did it already run?

    If caracas4check was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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-caracas4checkIN-MAL-2026-020568IN-MAL-2026-020567

References

Credits

  • Amazon Inspector · finder
  • 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.

Explore

caracas4check (PyPI) malicious package — MAL-2026-17198 | O3 Security