Which versions of syco1 are malicious?

The following npm versions of syco1 are flagged malicious: 1.0.3, 1.0.4, 1.0.5. Treat any of these as compromised.

How do I remediate syco1 if I installed it?

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

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

Yes — syco1 is associated with the IN-MAL-2026-007447, IN-MAL-2026-007445, GHSA-9mh8-xw8w-jh9g, IN-MAL-2026-009177 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 syco1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for syco1 (3 malicious versions).

Malicious package

syco1npm

Advisory published Jun 24, 2026Updated Jul 9, 2026

syco1 is a confirmed malicious npm package (MAL-2026-6404) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.3, 1.0.4, 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in syco1 (npm)

MAL-2026-6404

Immediate action

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

npm uninstall syco1

What this malware does

Package self-describes as a 'System binary configuration tool' but ships a covert screen and clipboard surveillance overlay. pointer.py captures full-screen JPEG screenshots (mss/ImageGrab), reads clipboard text on a 300ms loop (pyperclip.paste), and scrapes on-screen UI text from arbitrary windows via UI Automation; all captured data is POSTed unconditionally to a hardcoded author-controlled endpoint at https://new-pointer.vercel.app/api (pointer.py:33 VERCEL_API_URL). The destination is not configurable. The UX is built for concealment: an overrideredirect always-on-top transparent overlay (alpha 0.75, transparent-white) and hidden hotkeys including ctrl+q panic_exit (os._exit), esc stealth_hide, and 1+` stealth_show. The npm wrapper (index.js startApp) additionally performs a silent 'ghost install' of Python 3.12.3 from python.org into %TEMP% via curl, executed with /quiet InstallAllUsers=0 PrependPath=1 and comments explicitly describing the goal as 'No UI, No Admin Popup' — bootstrapping the Python runtime required by pointer.py without user consent. Any developer who runs the package's bin entry ships their clipboard contents, on-screen text, and screenshots of their primary monitor to the author's server. The shape is consistent with a proctoring-evasion / surveillance tool, not a sysadmin utility.

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.31.0.41.0.5

Indicators of compromise (SHA-256)

a187698defeffb7606287d65ed0e8979137b6869ab1be5c885520b7ea7291941

e43be65a0930b121cf4d610c70b2d07165e4d335dece4344590b471d078fa5b5

4cdfeaff9ba72cf95d0e701523049f137b60eadc9b54950e7c20ec3c87b59758

06c064916ff82d384123904da98de38a7b2b577ca59bcd94c7915b1eeb8c34c2

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for syco1 (3 malicious versions).
If you installed it — respond
syco1 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 syco1 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. syco1 on npm has been identified as a malicious package (versions 1.0.3, 1.0.4, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007447IN-MAL-2026-007445GHSA-9mh8-xw8w-jh9gIN-MAL-2026-009177

References

Credits

Amazon Inspector · finder

Detect & block this

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