shark-e2e-bnsneoPyPI
shark-e2e-bnsneo is a confirmed malicious PyPI package (MAL-2026-10912) that steals credentials and exfiltrates sensitive data (malicious versions 0.2.9, 0.2.10, 0.3.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in shark-e2e-bnsneo (PyPI)
What this malware does
On import, init.py decodes a base64-encoded string and passes it to exec() inside a _sync_module_docs() helper invoked at module top level. The decoded payload is a Windows-only ctypes call that displays a MessageBox (ctypes.windll.user32.MessageBoxW) and performs no network I/O, no filesystem reads of installer secrets, no credential access, and no persistence. The package metadata describes it as an end-to-end test artifact. The concern is the dispatch pattern itself — opaque base64-then-exec at import time is the obfuscated-code-execution shape and is unsafe regardless of today's payload, because the encoded blob is not human-reviewable and could change between releases. No attacker benefit is reachable in this version: the decoded code does not exfiltrate, drop, relay, or persist.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for shark-e2e-bnsneo (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shark-e2e-bnsneo across your stack and pipelines.
If you installed it — respond
shark-e2e-bnsneo 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 shark-e2e-bnsneo 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 shark-e2e-bnsneo 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
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks shark-e2e-bnsneo-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.