Install-time firewall · first to cover Go & the AI stack

Stop malicious packages
at the install, not the audit.

CyberXYZ Proxy is the install-time supply-chain firewall. A registry proxy intercepts every install, a decision brain reads the code at the commit level, and one dashboard governs inventory, SBOMs and integrations, across laptops, servers and CI/CD.

Book a 15-min demo See commit-level detection ↓

inline// verdict before install
commit// level of analysis
1// brain, every surface

ENFORCING 4/4 registries

ONLINE

ONLINE

ONLINE

⟳

xyz-npm-proxy ● live

npm install axios@1.14.1 403 BLOCK

pip install requests==2.32.0 200 ALLOW

npm install left-pad@1.3.0 451 QUAR

dotnet add package Newtonsoft.Json 200 ALLOW

tarball scan · commit-level analysis · inline on every install

live registry proxy (the firewall)

The firewall

A verdict on every install,
before it touches disk.

CyberXYZ sits in front of registry.npmjs.org, pypi.org and the rest. Every install from a routed machine or CI job is checked, npm tarballs (up to 5 MiB) are also scanned for install-script payloads, and the proxy returns allow, alert, quarantine or block before the install proceeds. One policy for every routed machine in the organization.

app.cyberxyz.io/proxy/findings

May 28, 10:40 AM npm

flatmap-stream@0.1.1 BLOCKED gha/CyberXYZ CI/CD Linux 172.184.213.226 CRITICAL

BLOCKED[known_malicious_version]Confirmed supply-chain attack: credential_stealer. Safe versions: 0.1.0CRITICAL

BLOCKED[vulnerability_match]GHSA-9x64-5r7x-2q53 · ranges ['= 0.1.1'] · fixed: noneCRITICAL

BLOCKED[vulnerability_match]GHSA-mh6f-8j2x-4483 · ranges ['>= 0'] · fixed: noneCRITICAL

May 26, 09:22 AM npm

axios@1.14.1 BLOCKED Mike’s MacBook DEV macOS 169.254.169.126 CRITICAL

BLOCKED[known_malicious_version]Confirmed supply-chain attack: RAT Dropper via compromised maintainer. Safe versions: 1.7.7, 1.7.6, 1.7.5CRITICAL

ALERT[vulnerability_match]GHSA-q8qp-cvcw-x6jj · ranges ['>=1.0.0', '<1.15.2'] · fixed: noneHIGH

QUARANTINE[version_jump_anomaly]axios jumped from 1.10.0 to 1.14.1 (skipped 4 minor versions overnight)MEDIUM

May 22, 12:15 PM npm

left-pad@1.3.1BLOCKEDgitlab/cyber CI/CD Linux34.139.136.251CRITICAL

May 22, 12:15 PM

go-weather-sdk@v0.4.0BLOCKEDgitlab/cyber CI/CD Linux34.139.136.251CRITICAL

May 22, 12:15 PM NuGet

AeroWizard.Net@2.3.1BLOCKEDgitlab/cyber CI/CD Linux34.139.136.251CRITICAL

May 22, 12:15 PM PyPI

durabletask@1.4.1QUARANTINEgitlab/cyber CI/CD Linux34.139.136.251MEDIUM

proxy findings (live capture from app.cyberxyz.io)

Commit-level detection

We read the code,
not just the scorecard.

Most "supply-chain" tools rate a package on project-health signals (OSSF scorecards). CyberXYZ does that and reads the actual change, line by line, commit by commit, so a malicious postinstall hook is caught the moment it lands, with no CVE required.

// across your repos

a3f9c2e chore: tidy build scripts 2 days ago

package.json

31 "scripts": {

32- "build": "tsc"

32+ "build": "tsc",

33+ "postinstall": "node ./.cache/setup.js"

XYZLifecycle hook added in a "tidy" commit. setup.js base64-decodes a payload and POSTs ~/.npmrc + env to 45.32.0.0/16. Verdict: BLOCK, no CVE required.

34 }

commit-level verdict (built mock)

Diff-aware

Every commit is parsed: added lifecycle hooks, network calls, obfuscation and file writes are scored, not just the manifest.

CVE

No CVE required

Malware is judged on behavior and intent, so a verdict does not have to wait for an advisory.

OSSF

Beyond OSSF scorecards

Proxy / repository managers stop at project-health signals. We add the actual code change on top.

MITRE ATT&CK tagged

Findings map to techniques, so your SOC sees them in language it already speaks.

The decision brain

Every surface asks
the same brain.

Editor, xyz Scanner, CI/CD and the runtime proxy all route to one decision engine and one verdict, inline on every install. See the full methodology →

01
Tarball & script scanBuffers the artifact and scans install hooks against known supply-chain patterns.
02
Commit-level analysisReads the actual code change for malicious behavior and intent, no CVE required.
03
Centrality & intelWeighs blast radius and live threat-intel across the dependency graph.
04
XYZ risk scoreSix dimensions collapse into one verdict: allow / alert / quarantine / block.

One dashboard

Machines, installs and verdicts,
in one place.

app.cyberxyz.io/fleet

Dev Machine 1 at risk

Mike’s MacBook Air0 blocked

Dev MachineDarwin169.254.169.126

0 installs · 34 scans

SSLProxyview details →

CI / CD 9 at risk

gha/CyberXYZSecurity/cyb…clean

CVSSLinux

31.146.211.20 · 32 installs

Proxyview details →

gha/CyberXYZSecurity/cyb…clean

CVSSLinux

128.66.193.5 · 32 installs

Proxyview details →

gha/CyberXYZSecurity/cyb…0 blocked

CVSSLinux

171.194.112.9 · 34 installs

Proxyview details →

gha/CyberXYZSecurity/cyb…clean

CVSSLinux

97.104.221.7 · 32 installs

Proxyview details →

gha/CyberXYZSecurity/cyb…clean

CVSSLinux

38.61.175.230 · 32 installs

Proxyview details →

gha/CyberXYZSecurity/cyb…clean

CVSSLinux

115.211.133.20 · 32 installs

Proxyview details →

cyberxyz-security/jdi…0 blocked

CVSSLinux

203.168.198.6 · 78 installs

Proxyview details →

ado/cyberxyz-test/age…0 blocked

CVSSLinux

38.226.207.101 · 3 installs

Proxyview details →

fleet overview (every machine, one place)

app.cyberxyz.io/notifications/15035

notification #15035 May 28 · 17:46 UTC

Blocked install: axios@1.14.1 on gha/CyberXYZSecurity/cyberxyz-platform · GitHub Actions 1000000333

0/10

XYZ SCORE critical · verdict block

SIGNALS

BLOCKED IN OUR OWN INSTALL LOG 0 blocked checks of axios@1.14.1, Apr 7 to Oct 7, 2026

gha/CyberXYZSecurity/cyberxyz-platform · GHA 1000000333 SBOM scanner dev laptop

STATEMENT Ecosystem npm · decision block (confidence 1.0) · machine gha/CyberXYZSecurity/cyberxyz-platform

SIGNALS · 2 of the 4 recorded

01Known Malicious VersionmatchedCRITICAL

Confirmed supply-chain attack: RAT dropper via a compromised maintainer, from our human-verified malicious-package intelligence. On its own, this decides block.

02Advisory MatchmatchedHIGH

GHSA-q8qp-cvcw-x6jj: prototype-pollution gadgets in the HTTP adapter (axios ≥1.0.0, <1.15.2). On its own, this decides alert.

PACKAGE CONTEXT

version 1.14.1 · published Mar 31, 00:21 UTC · removed by npm about three hours later · github.com/axios/axios · MIT

PACKAGE axios VERSION 1.14.1 ECOSYSTEM npm DECISION BLOCK

a real notification from our own CI on May 28, 2026, with two of its four recorded signals; the XYZ score is the one our API returns for this version today

Integrations

Plugs into the tools
your SOC already runs.

CyberXYZ Gates for GitHub Actions, GitLab CI and Azure DevOps, the VS Code extension, and high and critical alerts forwarded to Splunk, Elastic, QRadar, syslog or a signed webhook. Jenkins and any other CI that runs a shell work through xyz Scanner.

// top row: where it gates installs · bottom row: where alerts go

// book a demo

Watch it block a real attack. Then run it on your own installs.

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

What happens next

01A 15-minute callReal packages, real verdicts, and your questions.
02Connect one laptop or one pipelineOne setup command, or one line in CI. Under an hour.
03A 30-day proof of value on your own installsEvery signal, no card.

Not ready for a call?

Check any package, free, and see the verdict we would give it.

Try faker@6.6.6 ua-parser-js@0.7.29 express@4.21.2

Thanks! We'll be in touch.

Check your inbox. We'll reach out within 24 hours.

Stop malicious packagesat the install, not the audit.

A verdict on every install,before it touches disk.

We read the code,not just the scorecard.

Diff-aware

No CVE required

Beyond OSSF scorecards

MITRE ATT&CK tagged

Every surface asksthe same brain.

Machines, installs and verdicts,in one place.

Blocked install: axios@1.14.1 on gha/CyberXYZSecurity/cyberxyz-platform · GitHub Actions 1000000333

Plugs into the toolsyour SOC already runs.

Watch it block a real attack. Then run it on your own installs.

What happens next

Not ready for a call?

Thanks! We'll be in touch.

Where should we send the invite?

Stop malicious packages
at the install, not the audit.

A verdict on every install,
before it touches disk.

We read the code,
not just the scorecard.

Every surface asks
the same brain.

Machines, installs and verdicts,
in one place.

Plugs into the tools
your SOC already runs.