Which versions of nibra1 are malicious?

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

How do I remediate nibra1 if I installed it?

nibra1 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 nibra1 — how do I know if it already compromised me?

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

Yes — nibra1 is associated with the IN-MAL-2026-018393 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 nibra1 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 nibra1 (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 nibra1 across your stack and pipelines.

Malicious package

nibra1npm

nibra1 is a confirmed malicious npm package (MAL-2026-14284) 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 nibra1 (npm)

MAL-2026-14284

Immediate action

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

npm uninstall nibra1

What this malware does

The package's CLI entry (index.js) launches a Python payload (pointer.py) that registers global keyboard hooks, polls the clipboard, captures screenshots (mss / PIL.ImageGrab), and walks UI-Automation trees to extract on-screen text. Captured content is POSTed to the hardcoded endpoint https://iq-sec.vercel.app/api, which the installer never configured. Responses from that endpoint drive pyautogui / keyboard keystroke synthesis on the installer's host (force_paste bound to alt+v, mash-mode typing loops), turning server-controlled text into local keyboard input in the active window. To run the payload, index.js first attempts winget install Python.Python.3.12 --silent; on failure it silently downloads the python.org 3.12.3 Windows installer to %TEMP% and executes it with /quiet InstallAllUsers=0 PrependPath=1 under stdio: 'ignore', with in-source comments describing this as a 'Ghost Installer' with 'No UI, No Admin Popup'. A bundled start_tool.vbs uses Shell.Application.ShellExecute with window state 0 to launch pointer.py hidden in the background. The Python payload also constructs stealth Tk windows (empty titles, transparent overlays, overrideredirect) to hide its runtime UI.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4521ad8bc5159d00d7ab74f0911028637749bd2a7a346e8f134ad78ef8630aee

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 nibra1 (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 nibra1 across your stack and pipelines.
If you installed it — respond
nibra1 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 nibra1 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 nibra1 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. nibra1 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-018393

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nibra1-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