Which versions of bigtime are malicious?

The following PyPI versions of bigtime are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate bigtime if I installed it?

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.

I already installed bigtime — how do I know if it already compromised me?

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

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

Malicious package

bigtimePyPI

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)

MAL-2026-13712

Immediate action

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

pip uninstall bigtime

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

1 flagged

0.1.0

Indicators of compromise (SHA-256)

79fef30b8024966d3842e702f5f277b66d64b6a4a6af603c9eac0c720a4448d6

d14cc45326877547d5297956e4c2b5719122bcef140db0d7959e1b4da94e58d7

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

Campaign

2026-08-bigtimeIN-MAL-2026-017286

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database