Which versions of syboy are malicious?

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

How do I remediate syboy if I installed it?

syboy carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

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

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

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

Malicious package

syboynpm

syboy is a confirmed malicious npm package (MAL-2026-14212) that runs destructive / sabotage code (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in syboy (npm)

MAL-2026-14212

Immediate action

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

npm uninstall syboy

What this malware does

On invocation, index.js spawns start_tool.vbs via wscript.exe with detached/windowsHide flags; the VBS calls ShellExecute cmd.exe with the 'runas' verb and window state 0 to silently launch pointer.py under Administrator with no console, then the Node process exits leaving a hidden elevated background process. pointer.py reads the clipboard continuously, captures screenshots via mss/ImageGrab, walks the UI accessibility tree of foreground windows via uiautomation, and installs many global keyboard hotkeys via the keyboard module. The collected clipboard, screen, and UI content is POSTed to a hardcoded author-controlled endpoint at https://iq-overlay-pointer.vercel.app/api with no user-configurable destination. A Tk overlay is rendered with an empty title, transparent color, and overrideredirect to remain hidden from the user and screen-sharing. index.js additionally downloads the official Python 3.12.3 installer from python.org via curl to %TEMP% and runs it with /quiet InstallAllUsers=0 PrependPath=1 as a silent runtime dropper fallback when winget is unavailable, then deletes the installer.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f53c03163c0e0b47e20d28751745a66ecd1c9aadda7e96d648e8390ba49506f7

Detection & response playbook

Destructive / sabotage

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for syboy (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 syboy across your stack and pipelines.
If you installed it — respond
syboy carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If syboy 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 syboy 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. syboy 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-018306

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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