Repository navigation
Releases
QUANTUM-CLI v4.6.4
Full Changelog: v4.3.1...v4.6.4
QUANTUM-CLI v4.6.3
QUANTUM-CLI v4.6.3
The operator-surface release. The runtime modules that were placeholder
dashboards are now real probes, committed, and reachable from both the
CLI and the dashboard API.
The rule that governs all of it
A module may only report a capability it actually verified.
The placeholder dashboards returned a literal hardware_connected: True
with no probe behind it — a simulated capability, which this project's
"no simulated code" rule forbids. Every module now reports what the
host actually has, and says so when it has nothing. The rule is
enforced by tests: hardware_connected may only be True when a
device was actually found.
What the modules report now
| Module | Probe | Result on the reference host |
|---|---|---|
cve_update |
CISA KEV catalogue vs the local registry | 47 of 67 registered CVEs are known-exploited |
persistence_checker |
Run keys, startup folders, scheduled tasks, services, systemd, cron, LD_PRELOAD, modules | 731 artifacts (390 tasks, 323 services) |
traffic_analysis |
Interfaces, addresses, counters, capture tooling | 2 interfaces, 513 MB rx / 1.9 GB tx |
wallet (cryptowallet) |
Bounded filesystem search for wallet artifacts | 9 wallet files, 1 address, 16 keys |
pivot_lateral |
ARP/neighbour table + SMB, SSH, RDP, WinRM, LDAP, VNC | 15 neighbours |
vault_share |
Volumes, Cryptomator vaults, backups, SMB shares, NFS exports | 2 volumes, 1 vault, 6 shares |
cookie_manager |
Browser cookie stores, read from a copy, Netscape export | reads real Chromium SQLite stores |
mitm_dashboard |
Interception tooling, proxy env, proxy listeners, CA files | 2 proxy env vars |
c2_proxy |
Proxy env, OS proxy config, endpoint reachability | 2 env vars, egress tools found |
adb_exploit |
Real adb execution for every action |
no device attached (reported honestly) |
bluetooth / hid / sdr / imsi |
BT controller, HID devices, radios, capture-capable radios + modem | 1 controller, 38 HID devices, 0 radios |
dark_web_browser |
Tor binary, SOCKS/control ports, circuits | tor present, daemon down |
nso_pegasus_ios |
Device backups, MobileSync, pairing records, indicators | none found |
god_mode |
Real process privileges, effective user, importable modules | not admin, 5 modules |
ddos |
Live egress check, socket limits, NIC speed, stress tooling | egress yes, 2 tools |
mobile_verification |
Aggregates the mobile modules | 5 verified, 5 idle |
advanced_config_aggregator |
Aggregates the live states | 6 active, 6 idle |
openrouter_config |
Provider registry: endpoint, model, key present, free models, importable skills | 17 free models, 19/21 skills |
Reachability
CLI — 18 new operator commands, each with a --query sub-dispatch:
cve persistence cookiejar mitm traffic c2proxy autoconfig godmode
vault pegasus otp pivot mobile biometric wallet logclean adbx
advanced
plus the hardware probes bluetooth, hid, sdr, imsi. Two new
arguments: --port and --mode.
API — the operator modules are exposed under /api/{crypto, biometric, otp, logclean, adb, pivot, ddos, c2proxy, autoconfig, god_mode, darkweb, vault, nso_pegasus, mitm, rat, cve, mobile, cookie, traffic, persistence, advanced} (214 routes in total).
Safety fixes
logs/.lootkeyis now immutable by construction. Deleting or
editing it breaks every sealed.gfyinloot/. The key is refused
by name and hidden state files are not mutable either.- No log operation can escape
logs/. The old guard used
os.path.isabs, which does not mean the same thing on Windows —
/etc/passwdwas accepted and written outside the repository. - State-changing API routes are POST-only. Cleaning logs, injecting
cookies, deploying an APK and setting SMS forwarding were reachable
with a GET, which a browser prefetch, a link preview or a crawler can
trigger. - No GET route reads
request.json. That answers 415 for any
client that does not send a JSON body. - The log cleaner no longer searches the working directory by
default. A single dashboard request once stripped a header line
from 29 files in the source tree. - The payload manifest records byte counts, not character counts.
Three kernel stubs contain U+2014 — one character, three bytes — so
the manifest disagreed with the files it described.
Other fixes
- The
UiStatesealed class is no longer generic, which resolves the
Kotlin→JavaCAP#1wildcard-capture error that blocked
compileFullReleaseJavaWithJavac. @JavascriptInterfacemethods bridge the suspend repository calls
withrunBlocking— they run on the WebView JS thread, not a
coroutine.- ZIP payload archives are byte-reproducible: stored rather than
deflated (classic zlib and zlib-ng disagree byte-for-byte), a pinned
host field, and the manifest's volatile timestamp stripped. build_all_kernel.pygained the--outdirthe kernel-exploits
workflow was already passing; the job had been failing on every run.- The dirtypipe PoC defines
_GNU_SOURCEand includes<stdlib.h>
and<sys/types.h>(splice,F_GETPIPE_SZandloff_tare GNU
extensions).
Assets
| File | Size | Notes |
|---|---|---|
quantum-cli-full-4.6.3.apk |
15.9 MB | V2 signed, root-capable |
quantum-cli-limited-4.6.3.apk |
15.9 MB | V2 signed, no-root |
quantum-exploits-v4.6.3.zip |
213 KB | exploit modules + operator harness |
quantum-payloads-v4.6.3.zip |
88 KB | 64 built payload artifacts |
payloads.lock.json |
18 KB | sha256 manifest for every payload |
PLATFORM_INDEX.json |
21 KB | platform/exploit index |
Both archives are byte-reproducible: every entry is stored, stamped
with a fixed epoch and a pinned host field, so rebuilding the same tree
yields identical archives. Every artifact in
quantum-payloads-v4.6.3.zip matches payloads.lock.json by size and
sha256.
They are reproducible across platforms as well: the archives this
release was built from are byte-identical to the ones a Windows
checkout produces.
| Archive | sha256 (first 16) |
|---|---|
quantum-exploits-v4.6.3.zip |
8e150c825dfddd8a |
quantum-payloads-v4.6.3.zip |
01acf2c12b7d493a |
Rebuild with:
python package_release.py --version 4.6.3Verification
| Check | Result |
|---|---|
pytest tests/ |
667 passed, 10 skipped, 0 failed |
ruff gate (E9,F63,F7,F82,F401,F811) |
clean on the committed tree |
payload manifest vs payloads.lock.json |
64/64 verified |
apksigner verify |
V2 signature scheme on both APKs |
| GitHub CI | 9/9 jobs green |
Authorized use only
All tooling in this release assumes penetration-test, lab or
contracted-authorization contexts. Use it only against systems you own
or have written authorization to test.
QUANTUM-CLI v4.6.2
Quantum CLI v4.6.2
Release notes for the v4.6.2 line.
Highlights
- Android v4.6.2 APKs —
full(root-capable) andlimited(non-root) release
variants, both V2-signed and verified withapksigner. - ADB / FRP controller — real device control over
adb: QR pairing, shell
execution, FRP removal, contacts/SMS/call-log/keychain exfiltration, media
capture, APK install, backup. - HID payload generator — DuckyScript output for Hak5 Ducky, Bash Bunny v2,
O.MG cable, Cactus WHID 2 and BADUSB, with 12 pre-built attack vectors. - IoT dashboard — NRSuite-style device discovery (ESP32, Tenda, Wavlink,
D-Link, Belkin), MQTT/CoAP/Modbus protocol scanning, exploit payload generation. - Bash Bunny v2 generator — GUI workflow to DuckyScript conversion plus
natural-language prompt parsing. - VM/QEMU integration — launch Kali Linux in QEMU with HID device passthrough.
- Security tool catalog — one interface for Metasploit, Shodan, sn1per,
wifite3, Nmap, Burp Suite, AirCrack-ng, John and Hashcat. - Router exploits — completed
Session(cookie absorption + auth header) and
login()for password-based router auth.
Fixes
UiStatesealed class no longer generic — resolves the Kotlin→JavaCAP#1
wildcard-capture interop error that blockedcompileFullReleaseJavaWithJavac.- Stale generated
NativeGuiPattern.javaremoved from the source tree. Widget.Quantumtheme added; Material button styles corrected in
activity_quantum_native.xml;quantum_divider.xmland
quantum_bottom_nav.xmlcreated.- Registry folder-payload harness restored (
PAYLOADS_DIR,folderon 61
entries,needs_targeton 29,_fire_folderrunner) after v4.6.0 dropped it
while the operator suite still required it. - Bluetooth tier registered (CVE-2017-0781 / 0785, CVE-2018-5383, BLACKBED-BLE)
and resolved byresolve_weapon(). MALWARE-APK-WRAPPER-NECROregistry entry plusquantum.weapons.malwareprobe.brute/hashes: thebitcoin_walletformat was missing thesaltkey that
cracking_dashboard_state()reads.brute/vaults:veracrypt_header_password_check()now reports an honest
errorwhen the header invariants fail instead of returning a silent
ok=False.- Unused imports removed across
ops/,catalog/,crack/,weapons/,
agents/specialized/androuter_exploits.py.
Verification
| Check | Result |
|---|---|
pytest tests/ |
505 passed, 5 skipped, 0 failed |
ruff gate (E9,F63,F7,F82,F401,F811) |
clean on the committed tree |
gradlew assembleFullRelease assembleLimitedRelease |
BUILD SUCCESSFUL |
apksigner verify |
V2 signature scheme on both APKs |
aapt2 dump badging |
correct package names and version codes |
Assets
| File | Size | Notes |
|---|---|---|
quantum-cli-full-4.6.2.apk |
15.9 MB | V2 signed, root-capable |
quantum-cli-limited-4.6.2.apk |
15.9 MB | V2 signed, no-root |
app-full-release.apk |
15.9 MB | V2 signed, root-capable (CI build) |
app-limited-release.apk |
15.9 MB | V2 signed, no-root (CI build) |
quantum-exploits-v4.6.2.zip |
213 KB | exploit modules + operator harness |
quantum-payloads-v4.6.2.zip |
88 KB | 64 built payload artifacts |
payloads.lock.json |
18 KB | sha256 manifest for every payload |
PLATFORM_INDEX.json |
21 KB | platform/exploit index |
The two archives are byte-reproducible: every ZIP entry is stored
(uncompressed), stamped with a fixed epoch and a pinned host field, and the
manifest's volatile build timestamp is stripped. Rebuilding the same tree
yields identical archives, and every artifact in
quantum-payloads-v4.6.2.zip matches payloads.lock.json by size and
sha256.
Reproduce with:
python package_release.py --version 4.6.2Authorized use only
All tooling and documentation in this release assume penetration-test, lab or
contracted-authorization contexts. Use only against systems you own or have
written authorization to test.
v4.6.1 — deterministic payload builds (ZIP epoch pin) + refreshed assets
v4.6.1 — asset refresh on v4.6.0 (authorized lab use only)
Fixed
- Nondeterministic ZIP payloads: CVE-2023-42790.ipk and CVE-2024-36210.zip embedded wall-clock mtimes via zipfile.writestr, so every build hashed differently and CI lock-diff failed spuriously. Both builders now pin all entry timestamps to the ZIP epoch (1980-01-01) via fixed ZipInfo. Proven: two separate builds produce identical SHA-256.
- New regression test: test_zip_entries_pinned_epoch asserts no wall-clock mtime in any ZIP artifact.
Verified this release
- run_all.py build: 64 artifacts, verify 64/64 PASS, --diff against committed payloads.lock.json: clean (lock regenerated via make lock).
- tests/test_payloads.py: 51 passed.
Assets
- quantum-exploits-v4.6.1.zip — 73 exploit builders + harness (run_all, tv_sweep, callback_server, watch, kernel gate, offset resolver, tier1 gate, platform index + lock).
- quantum-payloads-v4.6.1.zip — all 64 built payload artifacts + manifest.json/md (byte-verified against dist/).
- PLATFORM_INDEX.json, payloads.lock.json standalone.
v4.6.0 — verified 61-CVE exploit set + 33 registry weapons + payload harness
v4.6.0 — exploit verification, reorg, registry + payload harness (authorized lab use only)
Verified
- All 64 Desktop CVE deploy.py modules compile clean, zero placeholder flags; raw-protocol implementations confirmed (e.g. stdlib SMB1/MS17-010 client).
- Removed: 186-file identical nested duplicate tree inside CVE-2024-4438; stray 1-byte copy artifact.
- Merged bare dirs into CVE-number+description homes (Baron Samedit .c, PwnKit .c, nftables .c — all real vendored PoCs, hash-matched with weapons/poc/src/).
- Replaced eight 1-byte stub inits with real package markers.
Reorganized (Desktop Exploits)
- zero-click_exploits/_cve/{android,bluetooth,browser,ios,messaging,network,webapp,wifi,windows}/ (49 CVEs)
- zero-day_exploits/_cve/{linux,network-device,windows}/ (12 CVEs)
- tools/ (20 tool dirs), archive/ (exploit-db-scale dumps)
Repo integration
- ZERO_DAY_REGISTRY: 29 -> 62 entries (15 real network probes in remote_v3.py, 18 zero-click staging checks in media_v3.py). Every entry resolves and fires without raising (verified against TEST-NET-1).
- exploits/: 73 payload-builder modules, run_all.py builds 64 hashed artifacts into dist/ (PASS 64/64 verify).
- Fixed: CVE-2026-106382 truncation bug, Windows CRLF hash drift on .c sidecars, fcntl guards for Windows, adb-TLS typo, catalog search()-shape crash, dist-archive registry parity (3 entries backported with implementations).
- CI: payloads.yml (build+test+verify+lock diff) and kernel-exploits.yml (compile gate).
Tests
- tests/test_payloads.py: 47 passed, 2 skipped (manifest-gated)
- tests/test_catalog.py + tests/test_registry.py: pass
- tests/test_dist_parity.py: pass
QUANTUM-CLI vv4.5.0
Full Changelog: v4.4.3...v4.5.0
QUANTUM-CLI v4.4.3
QUANTUM-CLI v4.4.3
Operator-suite feature release — camera feeds, Tasks workflows, floating
chat, zenmap scan controls, and real chat attachments.
Camera video thumbnails + live feed preview
- Every camera card now shows a real JPEG still as a 2×2-inch
clickable thumbnail with a centered play button — cyan when the
camera is CONTROLLED (creds cracked), dim when riding the
default-credential path. - Tapping opens a full-screen video feed preview: live stills
auto-refreshing every 3s over the camera's snapshot endpoints, LIVE
on/off toggle, manual refresh, per-frame timestamps, and honest
NO SIGNAL / FETCHING states (no fake video). - Thumbnails re-fetch after PTZ nudges and preview close so they never
show a stale view. Newops/CamPreview.ktengine (two-pass
inSampleSize decode, thumbnail cache, per-IP in-flight guard).
Tasks dashboard (workflows)
- New Tasks sidebar page: create, edit, delete, and run named
chains of/aicommands with${var}templating (ascanstep
auto-fillsfirst_host/first_camfor later steps). - Runs stop at the first failed step and report per-step results.
Seeded with recon-then-fingerprint / zero-check / camwar chains.
Floating chat bubble
- A cyan bubble in the bottom-right corner opens the popup AI chat from
any page (hidden on the Chat page itself).
Zenmap-style scan controls (Network page)
- Host scan with target CIDR or single host, port spec including ranges
(22,80,443,1000-2000), and nmap timing templates T0 paranoid →
T5 insane mapped to sweep concurrency and probe timeout. - Camera/ONVIF ports (554/8899) light up green in the results.
Pure logic unit-tested inops/ZenScan.kt.
Chat attachments + save-as
- Paperclip opens the system file picker (any file) or
photo/video picker; the new image icon goes straight to photos.
Picked files are copied intofiles/attachments; small text files
are inlined into the message so every AI mode can read them. - The download icon on each message now opens a save-as dialog —
any location, name, and extension — instead of a fixed
files/Downloads/*.txt.
Also
- In-app manual entries 13–17 documenting all of the above.
- All 67 Android JVM unit tests green; both APK flavors build clean.
QUANTUM-CLI v4.4.2
QUANTUM-CLI v4.4.2
Maintenance release — fixes the on-device AI model download and aligns the
Android app version with the release tag.
Fixes
- Local AI model download (HTTP 401 / 404) — both model mirrors baked
into the app died: Google retired themediapipe-assetsbucket path for
gemma-2b-it-gpu-int4.bin(404) and thelitert-communityHuggingFace
fallback became auto-gated (anonymous downloads get HTTP 401). The
downloader now uses three verified ungated HuggingFace mirrors of the same
Gemma-2B int4 TFLite artifact (~1.3 GB, GPU int4 first, CPU int4
fallbacks), all confirmed anonymously downloadable, with resume + mirror
failover unchanged. - Downloads now send a proper
User-Agentso mirrors don't throttle or
reject default Java clients. - Version alignment — the Android
versionNamewas still4.4.0
(versionCode 2) inside the v4.4.1 APKs, so the in-app update check kept
offering v4.4.1. Now4.4.2(versionCode 3), matching this tag.
Other changes since v4.4.1
- The Python-side
sim/simulation package (red/blue/purple team + network
simulation, training tooling) was removed from the app per operator
decision; it was never part of the operational C2 path. Suite: 117
passed, 2 skipped.
Notes
- Local AI needs ~1.3 GB free space; the download resumes automatically if
interrupted. Online and deterministic AI modes are unaffected.
QUANTUM-CLI v4.4.1
Full Changelog: v4.4.0...v4.4.1
QUANTUM-CLI v4.4.0 — Operator Suite
Quantum CLI v4.4.0 — Operator Suite
The zero-click audit release: every advertised exploit is live, honest,
and verifiable — plus the operator suite (providers, agents, skills,
workflows, Project Zero feed) on both Python and Android, the full
Exploit-DB catalog with hourly updates, and the Quantum C2 Tier-1
capability ports.
Highlights
Zero-click exploit audit (docs/ZERO_CLICK_AUDIT.md)
- CVE-2026-0073 — adbd TLS auth bypass (EC-cert vs stored RSA key):
the full TAO framework — STLS negotiation, TLS 1.3 with ephemeral
EC P-256 client cert, post-TLS shell via 32 MB delayed-ack window,
plus privilege escalation, lateral movement (WiFi/BT/contacts/SMS/
GPS), DNS/ICMP/HTTPS exfiltration, persistence, evasion, and DGA
C2. Verified end-to-end against a mock adbd. - 63 per-CVE payload folders verified (11 previously-empty folders
filled + 27 new + the original set): BlueFrag (CVE-2020-0022), BT
HID injection (CVE-2023-45866), KRACK (CVE-2017-13077), BootHole
(CVE-2022-21894), Follina (CVE-2022-30190), FORCEDENTRY
(CVE-2021-30860), WebKit UAF (CVE-2021-30858) + type confusion
(CVE-2023-32409), Apple ImageIO (CVE-2023-41064), libwebp
(CVE-2023-4863), WhatsApp VOIP (CVE-2019-3568), EternalBlue,
Zerologon, PrintNightmare, PetitPotam, ProxyLogon, and more. Every
deploy tool: JSON output, exit-code contract, never crashes,
structural self-verification. - 14 new zero-click delivery folders (2022–2026 chains): BlastPass
wallet (CVE-2023-41061), Exynos baseband (CVE-2023-24033), Samsung
baseband (CVE-2022-44319), Triangulation (CVE-2023-32434/32435),
WebKit ITW 2023/2025 (CVE-2023-42924, CVE-2025-24085), iOS kernel
(CVE-2024-23225), Intellexa (CVE-2024-4438/4439), Pegasus 2025
(CVE-2025-41300/41301), WhatsApp libmultiple (CVE-2022-27492),
Outlook NTLM leak (CVE-2023-23397 — real MS-CFB .msg), Office HTML
(CVE-2023-36884 — real OOXML + CAB/INF/DLL stage), EchoLeak
(CVE-2025-32711). - 13 perimeter zero-day folders (2021–2025): ProxyShell
(CVE-2021-34473), ProxyNotShell (CVE-2022-41040), Spring4Shell
(CVE-2022-22965), ForgeRock (CVE-2021-35464 — pure-Python Java
gadget chain, JVM-verified), PaperCut (CVE-2023-27350), GoAnywhere
(CVE-2023-0669), Ivanti EPMM (CVE-2023-35078), FortiManager
(CVE-2024-47575), ScreenConnect (CVE-2024-1709), SAP NetWeaver
(CVE-2025-31324), Citrix Bleed 2 (CVE-2025-5777), Ivanti Connect
Secure (CVE-2025-0282), regreSSHion (CVE-2024-6387). - Necro-class APK wrapper malware tool (
MALWARE-apk-wrapper- necro-class): wraps any Google-Play-sourced APK with a payload DEX
chained to the original app class via reflection (marker file +
optional TCP beacon), pure-Python AXML surgery + v1/v2 APK signing.
Verified withapksigner verifyexit 0 (build-tools 34.0.0) and
jarsigner -verifyon a 25.9 MB 12-DEX real APK. - Misattributed CVEs rejected — the supplied "iMessage
CVE-2023-34048"-class pairings (actually VMware/Splunk/Fortinet
CVEs) were not carried over as fiction.
Exploit catalogs (new)
- Exploit-DB in full — 47,160 exploits shipped as a gzipped CSV
seed (src/quantum/catalog/seeds/), synced hourly to
~/.qcli/catalog/; keyword/CVE/platform search + get-by-id
(python -m quantum exploitdb -q "CVE-2021-44228"). - PayloadsAllTheThings — 70-section/353-document index generated
from the live repo tree + repo ZIP sync with payload-text retrieval
(payloadscommand). - BadUSB pack — 20 operator-authored DuckyScript payloads (Hak5
Rubber Ducky / O.M.G Cable / Flipper Zero BadUSB equivalents):
reverse shells per OS, persistence, WiFi/SSH/LSASS exfiltration,
clipboard hijack, pranks (badusbcommand). - CISA KEV feed — live catalog (1,730 entries) with zero-click /
pre-auth indicator analysis (kevcommand;kev CVE-2025-0282
for a single lookup).
Quantum C2 Tier-1 ports (new)
quantum_android.py— the CVE-2026-0073 Android exploitation
framework (initial access → privesc → lateral → exfil → persistence
→ evasion → DGA C2).lockknife.py— LockKnife Android device forensics port (adb device
management, packages/settings/app-data extraction, screenshots).gitdork.py— stdlib GitHub dork search (61 classic dorks).sim/— 12 red/blue/purple team + network simulation classes
(training + playbook validation).ops/— real evasion (timestomp, masquerade, log purge, jitter),
exfiltration (DNS TXT tunnel with raw-socket DNS, HTTPS POST,
packaging) and persistence (Run key, scheduled task, startup folder,
cron, shell rc) plus an external tool catalog (toolscommand).- 34 operator skill playbooks imported from the Quantum C2 skill
library (c2.*PROMPT skills in Python; 8 seeded on Android).
Operator suite (Python)
providers— AI provider presets: Abliteration.ai, OpenRouter,
Venice.ai, Agnes, opencode (envQCLI_AI_PROVIDER+ per-provider
key vars).agents— SLDR sovereign-operator preset + NS-org agent presets
(ns-command/intel/craft/breach/deploy/forge/sensor/scribe), JSON CRUD.skills— PROMPT/TOOL/SCRIPT skill packs + prompt composition.workflows— CRUD +${first_host}variable-substitution runner.p0feed— Google Project Zero Atom feed: latest posts, zero-day
candidates, markdown rendering.- Weapons: Bluetooth tier (BlueBorne BNEP/SDP, KNOB, BlackBED BLE,
BlueFrag), ADB tier (CVE-2026-0073 STLS probe), KRACK — all wired
into the 64-entry ZERO_DAY_REGISTRY fire contract (folder weapons
forge offline payloads or probe targets via their deploy.py).
Operator suite (Android)
- Boot spine: 8-phase isolated boot, crash-loop guard, healing daemon,
safe mode (SafeModeActivity), health mesh, signed education content
(tooltips/walkthroughs, ECDSA-verified hotfix channel). - Provider presets for the AI client (Abliteration.ai/OpenRouter/
Venice.ai/Agnes/opencode) with per-provider keys. - Agents/Skills/Terminal pages, agent + skill + workflow stores
(+ c2.* playbook seeds). - Searchable exploit dropdown over the 100+ entry weapon registry
(new ZERO-CLICK/PERIMETER tiers) + Exploit-DB catalog search
(bundled 47k seed, hourlyCatalogSyncrefresh,exploitdb/
catalog_syncQcliApi commands). - Chat enhancements: per-message copy/download, attachments, floating
chat FAB. - Dashboard status chips (root/VPN/IP/MAC/DNS/proxy) + Project Zero
feed card + GitHub sidebar link. - Local model downloader: mirror fallbacks + resume + size sanity.
Testing
- Python: 100+ tests across the operator suite, catalogs, C2 ports,
and real modules (14 zero-click generators run end-to-end in CI; 18
perimeter/legacy probes verified against closed ports; APK wrapper
full-wrap test runs when the reference APK is built). - Android: unit tests for crash-loop guard, ledger bindings, content
signing, doctrine codex, widget layout; full + limited APK builds
(unit tests run before release builds in CI).
Docs
docs/ZERO_CLICK_AUDIT.md— the audit (findings, remediation,
honesty boundaries, second-sweep additions).docs/SLDR_AGENT_PROMPT.md— SLDR/NS-org agent doctrine.docs/ROADMAP_TASKS.md— operator task list / master roadmap.
Authorized engagements only. See README for usage.