bigtimePyPI
Advisory published Updated
bigtime is a confirmed malicious PyPI package (MAL-2026-13712) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigtime (PyPI)
What this malware does
The package presents itself as a time module wrapper, but its __init__.py invokes qwe900.init, which performs two exfiltration behaviors on import. First, _home_folders() enumerates the installer's Desktop, Downloads, and Documents directories and _find_all_files() walks them; a background thread tails file contents and POSTs them to a Discord webhook whose URL is stored base64-encoded in _WEBHOOK_B64 and decoded at import time. Second, init() replaces builtins.open process-wide with _patched_open, wrapping every returned file object in _WatchedFile; any subsequent write() on any file in the host process is copied to the same webhook. The embed title New Token Captured names the operator's intent to capture credentials and tokens flowing through the installer's own code. The base64-encoded destination and the time-wrapper cover story hide the exfiltration channel from casual source review.
The package contains hidden code to overwrite the built-in "open" function and exfiltrate every write to opened files. Exfiltration watcher is also attached to other files in user's home directory.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-08-bigtime
Reasons (based on the campaign):
- files-exfiltration
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for bigtime (version 0.1.0).
If you installed it — respond
bigtime 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 bigtime 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks bigtime-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.