Which versions of sypoi1 are malicious?

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

How do I remediate sypoi1 if I installed it?

Remove sypoi1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — sypoi1 is associated with the IN-MAL-2026-007444, IN-MAL-2026-007902, GHSA-25vm-7gph-35p5, IN-MAL-2026-009183 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 sypoi1 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 sypoi1 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sypoi1 across your stack and pipelines.

Malicious package

sypoi1npm

sypoi1 is a confirmed malicious npm package (MAL-2026-6405) that executes malicious code on install (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 sypoi1 (npm)

MAL-2026-6405

Immediate action

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

npm uninstall sypoi1

What this malware does

On require, index.js silently bootstraps a full Python runtime on the installer's machine — first via winget install -e --id Python.Python.3.12 --silent, falling back to downloading python-3.12.3-amd64.exe from python.org and executing it with /quiet InstallAllUsers=0 PrependPath=1 — then silently pip installs pyautogui, keyboard, mss, pillow, pyperclip, and uiautomation. It then spawns pointer.py, which installs system-wide hotkeys (Ctrl+C, Alt+S, F8/F9/F10, Alt+M, Ctrl+Q), creates a topmost transparent always-on-top Tk window using overrideredirect(True) to hide from the user, continuously monitors clipboard contents, and on hotkeys captures full-monitor screenshots and on-screen text via UI Automation. Captured clipboard text and base64-encoded screenshots are POSTed to a hardcoded destination at https://iq-overlay-pointer.vercel.app/api. The agent also exposes a mash_callback mode that hooks keyboard.on_press with suppress=True and substitutes attacker-supplied characters via pyautogui.write(char), injecting keystrokes into whatever window is focused. The package's declared purpose — "System binary configuration tool" by author "SysDev" with keywords system/binary/util/config — does not match any of this behavior; the metadata is a cover story for a screen/clipboard surveillance and remote-keystroke-injection agent.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

b22a9450e70ba1095097d2779ad6da01c111c37e940d890fbfc21d1aeb6a0f11

3915c6ac9deb9f7d6d26939bb46fbe5782646d9f146fea26ad1da3a05ef7dbae

8f75d2bf0f1e5af3bf0af9183ea1f44474eb92ce5349b75aaefa4a4b3aa2b3f6

65d949f015f5bb8d5053e1f138f9b90f74ae3de2ca88abff64a7554574f8faa6

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sypoi1 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sypoi1 across your stack and pipelines.
If you installed it — respond
Remove sypoi1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If sypoi1 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 sypoi1 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. sypoi1 on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007444IN-MAL-2026-007902GHSA-25vm-7gph-35p5IN-MAL-2026-009183

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sypoi1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database