dev-helper-bgPyPI
Advisory published Updated
dev-helper-bg is a confirmed malicious PyPI package (MAL-2026-10992) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.3, 0.1.4, 0.1.6…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dev-helper-bg (PyPI)
What this malware does
On import dev_helper, dev_helper/__init__.py calls start_decryptor() at module top level, which spawns a daemon thread running decrypt_and_run(). That function fetches an AES-GCM key from the hardcoded endpoint https://key-2qfm.vercel.app/api/key, uses SHA-256 of the fetched value as the key, reads the shipped dev_helper/encrypted.bin (nonce||ciphertext, 16897 bytes), decrypts it with AES-GCM, and passes the plaintext to exec(). The executed code is not present in cleartext in the package and can be rotated by whoever controls the Vercel endpoint or the shipped blob, giving arbitrary code execution on any host that imports the package. A separate bot.py also auto-starts a Telegram bot with a hardcoded token in a daemon thread on import, providing an out-of-band channel to the author. The encrypted-blob-plus-remote-key pattern serves only to hide the code that actually runs on the installer.
The package embeds encrypted code that, during import, is decrypted using an externally sourced password. The recovered code is executed and starts a bot capable of exfiltrating local files.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-07-make-helper
Reasons (based on the campaign):
-
files-exfiltration
-
obfuscation
-
uses-telegram-bot
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for dev-helper-bg (4 malicious versions).
If you installed it — respond
dev-helper-bg 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 dev-helper-bg 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 dev-helper-bg-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.