Which versions of adminbypasser are malicious?

The following PyPI versions of adminbypasser are flagged malicious: 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 2.0.1. Treat any of these as compromised.

How do I remediate adminbypasser if I installed it?

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

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

Yes — adminbypasser is associated with the 2026-02-old-adminbypasser 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 adminbypasser 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 adminbypasser (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging adminbypasser across your stack and pipelines.

Malicious package

adminbypasserPyPI

Malicious code in adminbypasser (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-774

Immediate action

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

pip uninstall adminbypasser

What this malware does

Package silently downloads remote code and adds its execution to the autostart. During analysis, the remote domain no longer existed.

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

Campaign: 2026-02-old-adminbypasser

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
peristence-autorun

Malicious versions

9 flagged

1.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.82.0.1

Indicators of compromise (SHA-256)

867991d0e6c74f15c2f231c002867172a4e03044a328676cf9b2ec07a7e48f68

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 adminbypasser (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging adminbypasser across your stack and pipelines.
If you installed it — respond
adminbypasser 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 adminbypasser 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 adminbypasser 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. adminbypasser on PyPI has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-02-old-adminbypasser

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks adminbypasser-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