ninja.ing
RANSOMWARE.NINJA
THE SUITE · ninja.ing

THE WHOLE LINE, NOT ONE SLICE

Detection stops at the alert. Backup starts after the encryption.

Ransomware is not one problem, it is six — and the market sells them as six products from six vendors who do not speak to each other. This is the whole line: predict the crew, catch the preparation, detect in your own SIEM, contain with a swarm, rebuild in dependency order, and prove every bit of it afterwards.

“If it lands on Friday, are we trading on Monday?”

Ten years of detection spend has not changed the answer. This suite is built around it.
—LEAK-SITE VICTIMS TRACKED
—ACTIVE CREWS
6hINGEST CADENCE
0OF YOUR LOGS WE HOLD

PREDICT

Who is coming for your sector, and which CVEs they actually exploit.

ransomware.ninja · Signal

PREPARE

Phase Alignment: the operator is staging. The last window before encryption.

DEATHSTAR

DETECT

Rules compiled to KQL or GuardDuty and run in your tenant.

Raz0r

RESPOND

A swarm hunts, contains and packages evidence with chain of custody.

V0id Agents

RECOVER

Blast radius becomes the rebuild scope, in dependency order, with a clock.

Sabaki · FUKKYŪ

PROVE

Dated, signed, append-only. Scored in public — including ours.

VERDICT

What we show you, in five minutes

Real data, live systems. The steps marked in build are honest about it.

1

The crews, live

Leak-site victims and crew dossiers, ingested every six hours. Public, no login, no NDA — you can check it before the call.

LIVE · ransomware.ninja
2

What they actually exploit

Pivot into a 10.5M-node graph: that crew's infrastructure, techniques and CVEs — with the traversal path shown, not asserted. KEV and EPSS weighted, so it reflects exploitation rather than CVSS theatre.

LIVE · Signal
3

The preparation, before the encryption

Phase Alignment watches for the temporal cluster of indicators that means an operator is staging to deploy. Everything after encryption is recovery; this is the last point where prevention is still on the table.

IN BUILD · DEATHSTAR
4

Detection in your SIEM, not ours

The rule compiles to KQL or a GuardDuty filter and executes in your own tenant under your credentials. We keep the query hash, a timestamp and a result count. Nothing else — no findings, no field values, no identifiers.

LIVE · Raz0r
5

What they could actually reach

Not single-hop blast radius: real asset-to-asset reachability, extended along identity as well as network. Then the fix is simulated on a digital twin and ranked by risk reduced, before anyone touches production.

LIVE · Sabaki · 1D
6

Assume it lands anyway

The blast radius becomes the recovery scope automatically. Rebuild in dependency order — identity before DNS, DNS before platform, platform before applications — in parallel waves, each gated by a five-layer health cascade so nothing is declared recovered because a VM booted. Ends with the hour you are trading again, and what warm standby would have saved.

IN BUILD · FUKKYŪ
7

Prove it

Our dated, public prediction about that crew — with the Brier score of every prediction we made before it. Download the ledger and verify it yourself with a script that imports nothing from us.

LIVE · VERDICT

Why nobody else answers this

THE SEAM NOBODY OWNS

Detection vendors stop at the alert. Backup vendors start after the encryption. The expensive part is the seam between them — knowing what broke, in what order to fix it, and when you are trading again. Blast radius answers what; the wave planner answers in what order. Joining them is the product.

PREVENTION HAS ONE WINDOW

Once encryption starts you are in recovery, whatever the marketing says. Phase Alignment aims at the staging period — the only stretch of the timeline where detection still prevents rather than documents.

ZERO MIGRATION

We never hold your telemetry. Detection executes in your Sentinel or GuardDuty under your credentials. Nothing to migrate, nothing to procure, and no data-residency conversation to stall the purchase for a quarter.

A TRACK RECORD YOU CAN AUDIT

Every forward-looking claim is registered before the outcome is known, on an append-only ledger, and scored in public whether it was right or wrong. No threat-intelligence vendor has ever published a Brier score. It is the one thing a competitor cannot copy without waiting two years.

Recovery, modelled properly

Recovery time is not one number per system. It is a posture decision, and boards are entitled to know what each option buys.

POSTUREWHAT EXISTS BEFOREHANDREALISTIC RECOVERY
COLDNothing. Tenancy, network and licences all on the critical path.Weeks. Procurement, not engineering, is the bottleneck.
WARMTenancy, runners and network pre-provisioned. Rebuild from infrastructure-as-code into ready-but-empty infrastructure.Days. The realistic enterprise target.
HOTStandby running and current.Hours. Expensive — reserve it for the genuinely critical few.

The output a board can act on is not a RAG chart. It is: these eleven components move you from weeks to days, they cost this much, and here is the rehearsal evidence that proves the plan works. That evidence is dated, signed and append-only — which is what NIS, your insurer and your auditor are all actually asking for.

See it against your own estate

The live feed is public — start there, today, with no conversation. When you want the other five stages pointed at your environment, that is a conversation with the person who built it.

OPEN THE LIVE FEED → EXPLORE THE GRAPH