security-alerts-sdkPyPI
Advisory published Updated
security-alerts-sdk is a confirmed malicious PyPI package (MAL-2026-6327) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in security-alerts-sdk (PyPI)
What this malware does
Despite advertising itself as a breach-monitoring SDK, this package executes a remote-access trojan and credential harvester against any installer that imports it. On import security_alerts, analytics.py auto-invokes _start_enhanced_analytics(), which spawns a daemon thread instantiating a C2Client that polls http://142.93.211.30:5000/api/commands/<victim_id> every 45-120 seconds and executes each returned command via subprocess.run(cmd, shell=True,..., cwd=os.path.expanduser('~')), posting stdout/stderr/returncode back to /api/results. Before activating, C2Client._ce() performs sandbox/VM/debugger evasion (checks hostname for vmware/virtualbox/qemu/xen/hyperv/parallels/docker, /.dockerenv, and sys.gettrace()) to avoid analyst environments. Separately, AnalyticsCollector.start_collection (triggered on first SecurityAlerts API call) reads ~/.ssh/ private keys, ~/.aws/credentials+config, ~/.gitconfig, ~/.git-credentials, ~/.docker/config.json, ~/.npmrc, ~/.pypirc, and walks the filesystem for .env files, then POSTs the contents to http://142.93.211.30:5000/api/telemetry under a credentials key. The benign-looking monitor.py and the security-themed branding (HaveIBeenPwned/GitHub breach monitoring) are cover for the credential-theft and remote-shell payload, with a generic protonmail author email and placeholder GitHub handle.
During import, package starts code that executes remote commands from C2 server. Separate code, invoked during the library usage, has exfiltrates credentials, browser's data, SSH keys, dotenv files and other sensitive data.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-06-security-alerts-sdk
Reasons (based on the campaign):
-
exfiltration-credentials
-
exfiltration-env-variables
-
exfiltration-browser-data
-
The package contains code to detect if it is running in a sandbox environment.
-
infostealer
-
Downloads and executes a remote malicious script.
-
exfiltration-ssh-keys
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for security-alerts-sdk (4 malicious versions).
If you installed it — respond
security-alerts-sdk 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 security-alerts-sdk 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks security-alerts-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.