Lethal Trifecta Guard: evidence, proof and selling tools

Official CAIN-42 IHVRK · New to this product? Learn it first

Don't trust CAIN-42. Verify CAIN-42. This is the Independent Human Verification Resource Kit for Lethal Trifecta Guard: every claim its page makes, as the exact request and the answer it must give, recorded live and signed. You check it on your own machine with a short Python script that uses no CAIN-42 code.

Every claim matched when recorded

Download the kit (.zip)

Everything you can give a customer

Selling tools

Pitch, emails, call script, objection answers, one-page summary, proposal.

Evidence pack

The figures and a ready email to an auditor or security reviewer.

Answers to buyer questions

Paste into a security questionnaire: YES, PARTIAL, NO or ASK.

Figures & benchmarks

Every number from the signed record, ready for a spreadsheet.

The kit

Kit	`lethal-trifecta-guard-20261103T225201`
Recorded	2026-11-03T22:52:01+00:00 against cainstudio.online
Claims	6
Zip SHA-256	`88c4afaa08d89a78d6ff000c2c75d1d2dc0e8658ed2b8dfb5c569c555737131c` (also in SHA256SUMS)
Signing key fingerprint	`1cacdfc1fc2024b6bb4f8fb02c7c80f4a57f44c5adb11c507190781b5d613de3`, published on cainstudio.online · mcpgate.online · clawx.click

Verify it on your own machine

unzip cain42-ihvrk-lethal-trifecta-guard.zip && cd cain42-ihvrk-lethal-trifecta-guard
python3 verify.py            # offline: hashes, Ed25519 signature, recorded answers
python3 verify.py --live     # also re-send every request yourself and check the answers now

A claim that cannot be checked counts as a FAIL, never a pass. The live check is the one that depends on nothing we recorded.

The claims in this kit

#	Claim	Answer must contain
C01	Control: internal report to your own domain -> No untrusted content, approved destination: everything runs.	`["ALL_STEPS_ALLOWED"]`
C02	A public GitHub issue leaks a private repository -> Modeled on a 2025 disclosure about a GitHub MCP server.	`["LEAK_PATH_BLOCKED"]`
C03	An email turns an image link into a leak -> Modeled on a 2025 vulnerability in an office AI assistant (CVE-2025-32711).	`["LEAK_PATH_BLOCKED"]`
C04	One database tool holds all three legs -> Modeled on a 2025 database-MCP support-ticket leak.	`["LEAK_PATH_BLOCKED"]`
C05	An API key smuggled out in base64 -> No injection needed; the disguised key is recognised.	`["LEAK_PATH_BLOCKED"]`
C06	Same report, attacker's address -> Identical to the control except the destination; customer rows recognised by fingerprint.	`["LEAK_PATH_BLOCKED"]`

Evidence links you can give your customers

Kit download: /proof/bundle/ihvrk-kits/cain42-ihvrk-lethal-trifecta-guard.zip
Each file on its own: README.txt · claims.json · transcript.json · MANIFEST.json · MANIFEST.sig · kit-key.json · verify.py
Run the live demo yourself on any of the three sites: cainstudio.online · mcpgate.online · clawx.click
The product explained: /guide-lethal-trifecta-guard.html · what it does not do: limits
Signing key on three independent domains: cainstudio.online · mcpgate.online · clawx.click
Three ready-to-send evidence pages: 1. Evidence pack · 2. Answers to buyer questions · 3. Figures & benchmarks
Every kit: all IHVRKs · machine-readable index

Send this to your customer

Don't take our word for it. Verify Lethal Trifecta Guard yourself:
1. Download the official CAIN-42 IHVRK: https://cainstudio.online/proof/bundle/ihvrk-kits/cain42-ihvrk-lethal-trifecta-guard.zip
   SHA-256: 88c4afaa08d89a78d6ff000c2c75d1d2dc0e8658ed2b8dfb5c569c555737131c
2. Unzip it and run: python3 verify.py --live   (Python 3, standard library only, no account)
3. Check the signing key fingerprint 1cacdfc1fc2024b6bb4f8fb02c7c80f4a57f44c5adb11c507190781b5d613de3
   matches https://cainstudio.online/evidence-kit-key.json, https://mcpgate.online/evidence-kit-key.json and https://clawx.click/evidence-kit-key.json
Live demo: https://cainstudio.online/guide-lethal-trifecta-guard-lab.html
What it does not do: https://cainstudio.online/guide-lethal-trifecta-guard-limits.html

What this kit is, and is not

It shows what the live product answered to these inputs, and lets anyone check that again. It is not a third-party audit, a certification, or a promise about inputs not listed. The product's limits page lists what it does not do.