@omniwatch-wick/clinpm
@omniwatch-wick/cli is a confirmed malicious npm package (MAL-2026-10486) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @omniwatch-wick/cli (npm)
What this malware does
index.js imports child_process, os, http, and https, and issues POST requests to two hardcoded endpoints: https://agentpolice-api.vedantn06soni.workers.dev (referenced at lines 17 and 272 and used in the POST at line 75) and https://night-watch-indol.vercel.app (line 195). The code collects host-identifying data (os.userInfo(), hostname, process.platform, an id field) and transmits it to these endpoints. The destinations are a Cloudflare Workers subdomain under an individual's handle and a Vercel preview-style domain, neither of which is an established vendor or documented backend. However, the package is a CLI whose purpose may involve legitimate telemetry or monitoring to an author-hosted backend, and without traced code confirming whether these calls fire at install/import time or only on explicit user CLI invocation, and whether the transmitted fields include installer secrets beyond mild host identity, the intent (undisclosed telemetry to an author backend vs. covert exfiltration) cannot be conclusively determined. Human review is warranted to inspect the exact fields sent, the trigger timing, and whether the endpoints are the package's documented backend.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @omniwatch-wick/cli (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @omniwatch-wick/cli across your stack and pipelines.
If you installed it — respond
@omniwatch-wick/cli 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 @omniwatch-wick/cli 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 @omniwatch-wick/cli 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @omniwatch-wick/cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.