Which versions of cyberday26szymon-auth are malicious?

The following PyPI versions of cyberday26szymon-auth are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate cyberday26szymon-auth if I installed it?

Remove cyberday26szymon-auth from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed cyberday26szymon-auth — how do I know if it already compromised me?

If cyberday26szymon-auth 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.

Is cyberday26szymon-auth part of a known attack campaign?

Yes — cyberday26szymon-auth is associated with the RLMA-2026-02096 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 cyberday26szymon-auth across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cyberday26szymon-auth (version 0.0.1).

Malicious package

cyberday26szymon-authPyPI

Advisory published Jul 7, 2026Updated Jul 9, 2026

cyberday26szymon-auth is a confirmed malicious PyPI package (MAL-2026-7452) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cyberday26szymon-auth (PyPI)

MAL-2026-7452

Immediate action

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

pip uninstall cyberday26szymon-auth

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

10c66b98bff4c49a43b8696a52e9d9bee7afee4ab0ae81a6b5c5174c674bf057

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for cyberday26szymon-auth (version 0.0.1).
If you installed it — respond
Remove cyberday26szymon-auth from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If cyberday26szymon-auth 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. cyberday26szymon-auth on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02096

Credits

ReversingLabs · finder

Detect & block this

O3 blocks cyberday26szymon-auth-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database