Which versions of timestamp-py are malicious?

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

How do I remediate timestamp-py if I installed it?

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

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

Yes — timestamp-py is associated with the 2026-04-process-support 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 timestamp-py 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 timestamp-py (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 timestamp-py across your stack and pipelines.

Malicious package

timestamp-pyPyPI

Malicious code in timestamp-py (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3136

Immediate action

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

pip uninstall timestamp-py

What this malware does

During import, the package automatically downloads and executes code that first acts as an infostealer and then starts code acting as a RAT. It connects with a hardcoded C2 server and waits for commands, supporting e.g. executing remote commands, exfiltrating files, recording the screen, executing GUI actions through PyAutoGUI.

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

Campaign: 2026-04-process-support

Reasons (based on the campaign):

exfiltration-generic
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
rat
spyware-like
infostealer
persistence
exfiltration-browser-data
exfiltration-crypto
files-exfiltration

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

ad3ae8b42c6902cd379c732765f0dab1aa53b3aad3b3e97ca6606edb83637ee6

d48be8ff856b19622d8bc8417db82b8752c41fb88aec5cd89d04bbee1bc729ef

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 timestamp-py (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 timestamp-py across your stack and pipelines.
If you installed it — respond
timestamp-py 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 timestamp-py 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 timestamp-py 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. timestamp-py 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-04-process-support

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks timestamp-py-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