Which versions of syspo are malicious?

The following npm versions of syspo are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate syspo if I installed it?

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

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

Yes — syspo is associated with the IN-MAL-2026-007446, IN-MAL-2026-010878, IN-MAL-2026-014737, IN-MAL-2026-017646, IN-MAL-2026-018249 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 syspo 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 syspo (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging syspo across your stack and pipelines.

Malicious package

sysponpm

syspo is a confirmed malicious npm package (MAL-2026-6406) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in syspo (npm)

MAL-2026-6406

Immediate action

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

npm uninstall syspo

What this malware does

Package is published under the cover story 'System binary configuration tool' but its actual behavior is a Windows surveillance dropper. On invocation, index.js silently installs a Python 3.12 runtime (via winget or by curling https://www.python.org/ftp/python/3.12.3/python-3.12.3-amd64.exe to %TEMP% and running it with /quiet InstallAllUsers=0 PrependPath=1) and pip-installs a surveillance toolchain (pyperclip, keyboard, requests, pillow, mss, pyautogui, pywin32, uiautomation, comtypes). A bundled start_tool.vbs is then launched detached with windowsHide, invoking Shell.Application.ShellExecute with verb 'runas' and windowStyle 0 to run cmd /c cd /d <dir> && python pointer.py elevated and with no visible window. pointer.py registers global keyboard hotkeys, captures screen regions with mss and PIL.ImageGrab, walks the foreground window's UIAutomation tree to extract text from EditControls, TextPattern DocumentRange, and LegacyIAccessiblePattern (routinely capturing browser fields, password inputs, and arbitrary application text), base64-encodes screenshots, and POSTs the harvested data via requests.Session to the hardcoded endpoint https://new-pointer.vercel.app/api which the installer did not configure. Source comments explicitly label the stages 'GHOST INSTALLER', 'VBSCRIPT STEALTH MODE', and 'HACK 1/2'. Transparent topmost tk windows with blank titles, overrideredirect, and 1x1 dot labels are used to hide the running surveillance UI from the user.

Malicious versions

5 flagged

1.0.01.0.11.0.21.0.31.0.4

Indicators of compromise (SHA-256)

6f89c590b7c90182cb86bc3e45f71f2357003f4359b6e94818fc996951762f5c

fbbc3c818ac60904428b280a60e6783a185a7fb00ef9c4f88c917426f2fca744

a71d0860e02e48cbb25260208399f44cd0ce1c30dc34557ed0dd74460db5fb0f

fb7a5e26944b2ef77f980764c721329874d9485147bcb1cba37471fb00ebdc02

6e90cf048bcfbc5fcc4108def74bee85be749c8f388aa2b93b4281af3808a2a1

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

Campaign

IN-MAL-2026-007446IN-MAL-2026-010878IN-MAL-2026-014737IN-MAL-2026-017646IN-MAL-2026-018249

References

Credits

Amazon Inspector · finder

Detect & block this

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