Which versions of bqq1 are malicious?

The following npm versions of bqq1 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate bqq1 if I installed it?

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.

I already installed bqq1 — how do I know if it already compromised me?

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

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

Malicious package

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)

MAL-2026-14164

Immediate action

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

npm uninstall bqq1

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

c8709cb6f826b8ee95c1d8aef1bb12c769c165260483b6a95be782af9dbeb2ba

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 bqq1 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bqq1 across your stack and pipelines.
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 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 bqq1 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. bqq1 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018234

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database