bqq1npm
bqq1 is a confirmed malicious npm package (MAL-2026-14164) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bqq1 (npm)
What this malware does
The npm package bqq1 advertises itself as a 'System binary configuration tool' but ships a covert surveillance and remote-control payload. On require/start, index.js unconditionally executes startApp(), which silently installs Python 3.12 (via winget, or by downloading the python.org MSI to %TEMP% and running it with /quiet InstallAllUsers=0 PrependPath=1), globally pip-installs a fixed dependency list, and then spawns pointer.py without any prompt, consent, or README documentation. pointer.py installs global keyboard hooks, reads the clipboard via pyperclip, captures screen regions using mss and PIL ImageGrab, and walks the Windows UIAutomation tree to scrape text from other applications' UI. The captured data is POSTed to the hardcoded endpoint https://iq-sec.vercel.app/api. The response body from that endpoint is fed into pyautogui, which types the remote-controlled text into whatever window is focused on the host, driven by global hotkeys (trigger_api, force_paste, retry_api). The UI runs in borderless Tk windows with blank titles, overrideredirect, and transparent overlays, plus 'stealth_hide' and 'panic_exit' hotkeys — explicit stealth engineering that contradicts the package's declared purpose.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for bqq1 (version 1.0.0).
If you installed it — respond
bqq1 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 bqq1 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
Detect & block this
O3 blocks bqq1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.