Case studies

Real attacks,
traced step by step.

Real supply-chain incidents, traced step by step, and where the CyberXYZ firewall blocks them at install, including the cases where we were late.

// AI model security · GenAI supply chain · transitive RCE

pyannote and the package it never named

Eight speaker-diarization models named one clean package. One hop below it, lightning 2.6.5 carried a checkpoint-loading RCE until 2.6.6 fixed it on Sep 10, 2026. We connected GitHub's advisory to these models by reading the whole install, not the manifest.

8 models26.6M downloads, 30 days7.8 CVSS
Read the case study →
// npm · DPRK RAT dropper

axios@1.14.1 RAT dropper

A compromised maintainer shipped two malicious axios tags that pulled in a North Korean RAT dropper. Blocked at install by CyberXYZ since April 2026.

~100M weekly downloads174K dependent packages~3 hrs exposure window
Read the case study →
// npm · worm · credential theft

Mini Shai-Hulud AntV npm worm

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 Endor Labs' public disclosure; the case study covers what we changed.

323 packages639 bad versions27 min window
Read the case study →
// 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

  1. 01A 15-minute callReal packages, real verdicts, and your questions.
  2. 02Connect one laptop or one pipelineOne setup command, or one line in CI. Under an hour.
  3. 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.

npm

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

Thanks! We'll be in touch.

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

Where should we send the invite?

  • 15 minutes
  • Video call
  • Times in your time zone

We reply within 24 hours to set a time.

We only use these details to arrange the call. Privacy policy