Which versions of saaa9 are malicious?

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

How do I remediate saaa9 if I installed it?

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

If saaa9 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.

Is saaa9 part of a known attack campaign?

Yes — saaa9 is associated with the IN-MAL-2026-018367 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 saaa9 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for saaa9 (version 1.0.0).

Malicious package

saaa9npm

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

MAL-2026-14254

Immediate action

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

npm uninstall saaa9

What this malware does

The package is published as a 'System binary configuration tool' but the shipped code is a covert Windows surveillance overlay. On execution, index.js spawns wscript.exe against the bundled start_tool.vbs, which uses Shell.Application.ShellExecute with the 'runas' verb and window state 0 to relaunch cmd.exe silently as administrator and run the bundled pointer.py. If Python is missing, index.js first silently installs Python via winget or, failing that, downloads python-3.12.3-amd64.exe from python.org to %TEMP% and executes it with /quiet InstallAllUsers=0 PrependPath=1, deleting the installer afterward. pointer.py registers global keyboard hotkeys and, on trigger, captures the installer's clipboard, screenshots regions of the active desktop, extracts on-screen text via IAccessible2/UIAutomation, and POSTs the collected data through a persistent requests.Session to the hardcoded endpoint https://iq-overlay-pointer.vercel.app/api. Server responses are auto-typed or pasted back into the active window via pyautogui. The tkinter UI is deliberately concealed (overrideredirect, empty title, transparent color, alpha 0.75, withdraw), and comments labeled 'HACK 1/2' confirm intentional stealth. The package metadata's stated purpose does not correspond to any of the observed behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3011e5a125f4db4febea1bf6778ed69ebb11009d2a1b119a46118822f3ef6e93

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for saaa9 (version 1.0.0).
If you installed it — respond
saaa9 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 saaa9 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

No. saaa9 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-018367

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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