Every npm, pip, Go and NuGet install goes through the CyberXYZ proxy and gets a verdict before it downloads. The same tool audits what is already installed, scans your code and gates CI.
macOS, Linux and Windows
real verdicts for every version shown; status codes as the npm proxy returns them
A malicious release runs its install script on the machine that fetched it, often before any advisory exists. A scanner that reads the lockfile afterwards reports what already ran. xyz puts the verdict in front of the install.
A compromised maintainer shipped two malicious axios tags that pulled in a North Korean RAT dropper. Blocked at install by CyberXYZ since April 2026.
One stolen npm token poisoned 323 packages across the AntV namespace in 27 minutes, with a credential harvester wired to run before any user script. Blocked after the first public disclosure; the case study covers what we changed.
On PyPI, the Hades worm poisoned PyPI projects with a .pth startup hook. CyberXYZ raised in-app HIGH alerts about 30 minutes after the wave began, hours before the first public advisory.
sudo xyz proxy setup --system routes every package manager through the proxy and installs an agent that keeps it that way.
Does each machine actually send installs through the proxy? From each agent's own check-in.
Every machine with an agent is routed and checking in.
Agent versions are compared with v1.4.69, the newest agent in your fleet.
What changed, newest first.
qa-mac-04 back after 30 hours; every package manager routesdev-laptop-21 yarn config restored to the proxyci-runner-3 express 5.1.0 could not be verified: 503, retry in a minutebuild-runner-02 after xyz upgrade, by itselfdev-laptop-07 npm config restored to the proxythe Machine coverage card rebuilt from the dashboard home (HomeCards.tsx); the event feed is an illustration of what the platform records: each agent's routing report and repairs, its version, and the proxy install log. Machine names are fictional.
The proxy covers installs from now on. xyz audit checks everything installed before. xyz fix plans the upgrade and never edits a lockfile.
real output, VS Code Dark Modern terminal; --write shows a diff and asks first
macOS
the XYZ Scan card, rebuilt from the dashboard with a real xyz audit npm upload; names changed
One command for the lot. xyz audit uploads npm, Python, every venv, Go, IDE and browser extensions and system packages as separate cards, so the dashboard can re-check them as new intelligence arrives.
xyz code-scan all runs open-source engines plus CyberXYZ's own supply-chain rules. It scans only what git would commit, redacts every secret, and never calls a partial run clean.
real output; PATH and INSTALL columns trimmed
xyz Scanner, the VS Code extension, CI and AI coding agents ask the same engine, and every run lands on the same dashboard.
on the dashboard: machine audits, fix plans, code scans and CI gates by machine and by person; secrets triage; Scan now
What reaches the dashboard The VS Code extensionProtect routes the job's own installs through the proxy, so a malicious version is refused on the runner. Scan gates on the lockfiles and exits non-zero on anything that should never ship.
uses: CyberXYZSecurity/depalert-action@v1, one line; mode: protect early, the default scan as the gateThe gitlab.com/cyberxyz/depalert catalog componentAzure and the rest: eval "$(xyz ci protect)" before installs. xyz ci init writes the pipeline file.Different jobs on the same supply chain. Run them together.
xyz mcp install --client all gives Claude Code, Cursor, VS Code, Devin Desktop (formerly Windsurf), Codex and Gemini CLI the CyberXYZ tools. With --hooks, Claude Code is denied installs of blocked or quarantined packages.
No install? The hosted server is https://mcp.cyberxyz.io/mcp.
xyz checkThe proxy's verdict for one package version, before you add it.
xyz fixThe nearest clean release per flagged package; --write shows a diff and asks.
xyz impactWho depends on a package, and whether this project reaches it.
xyz sbomCycloneDX 1.5 or SPDX 2.3 from your lockfiles, with advisories, EPSS and KEV.
xyz audit modelsLocal model files hashed and HF references found, never unpickled.
xyz remediate runRuns removals an admin approved in the dashboard.
xyz command.or pip install cyberxyz-scanner · later, xyz upgrade
xyz login, then approve a one-time code with your usual sign-in, MFA, SSO or passkey. The session lasts 90 days from last use.sudo xyz proxy setup --system routes every package manager and installs the agent. Fleets enroll with an MDM token.xyz proxy status: every tool routed, the lock on, the agent current.real output; machine name changed; per-tool config block, Detail column and state path trimmed
xyz audit for the whole machine, xyz fix in a project, xyz code-scan all before you push.xyz mcp) · included in every plan, see pricing · Maven: single packages with xyz check PACKAGE VERSION -e maven; Maven project audits are not available yet · in the editor, use the VS Code extensionBook 15 minutes. We run real packages through CyberXYZ while you watch, including axios 1.14.1, a hijacked release that dropped remote-control malware in March 2026, and show you exactly what your team would see. Then we connect one laptop or one pipeline for a 30-day proof of value.
Check any package, free, and see the verdict we would give it.
Check your inbox. We'll reach out within 24 hours.