chimera-sandbox-extensionsPyPI
Malicious code in chimera-sandbox-extensions (PyPI) Remove it immediately and rotate any exposed credentials.
What this malware does
When started, the code attempts to access multiple domains based on the generating algorithm. Once one valid is found, it downloads a script and executes it. The script collects data about the environment (e.g. attempts to get cloud tokens from the metadata URLs, collects some env variables) and sends them further to the remote target, which then decides about next stage code.
It may be targetting https://engineering.grab.com/chimera-sandbox
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2025-06-chimera-sandbox-extensions
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.
-
Downloads and executes a remote malicious script.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chimera-sandbox-extensions (version 0.1.42). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chimera-sandbox-extensions across your stack and pipelines.
If you installed it — respond
chimera-sandbox-extensions 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 chimera-sandbox-extensions 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 chimera-sandbox-extensions 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
Campaign
References
Credits
- Kamil Mańkowski (kam193)
Detect & block this
O3 blocks chimera-sandbox-extensions-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.