Which versions of sysc1 are malicious?

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

How do I remediate sysc1 if I installed it?

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

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

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

Malicious package

sysc1npm

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

Malicious code in sysc1 (npm)

MAL-2026-14214

Immediate action

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

npm uninstall sysc1

What this malware does

Package declares itself a 'System binary configuration tool' but ships a coordinated surveillance payload. package.json main is index.js which invokes startApp() at top level; on require or npm start, index.js silently installs Python (via winget or a fetch of python-3.12.3-amd64.exe run with /quiet InstallAllUsers=0 PrependPath=1), pip-installs keyboard, pyautogui, mss, uiautomation, and pywin32, then spawns the bundled pointer.py. pointer.py creates a topmost transparent overrideredirect Tk overlay (alpha 0.75) with multiple stealth hide/show/panic-exit global hotkeys, captures screenshots via ImageGrab/mss, reads the clipboard, and walks the UI trees of other running applications (including a documented 'CHROME BYPASS' that increases uiautomation WalkControl depth to scrape text out of Chrome). The captured screen contents, clipboard data, and text harvested from unrelated applications are POSTed with requests.Session to the hardcoded author-controlled endpoint https://new-pointer.vercel.app/api. The advertised package purpose is inconsistent with the shipped behavior; the stealth overlay, global hotkeys, cross-application UI scraping, silent Python bootstrap, and hardcoded exfiltration endpoint together form an on-load surveillance dropper.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

10a1bd2fc9346795fad18a8ea925bc9e04c696a7777bdc6e71fefc9836bc948a

2246c45afa73830233fa107ca0b97d96b10b59169599d248f7327d4e5317ff9f

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

Campaign

IN-MAL-2026-018311IN-MAL-2026-018309

References

Credits

Amazon Inspector · finder

Detect & block this

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