LAB 01
API authorization across tenants
An intentionally vulnerable and corrected Node.js API with SwiftUI and Kotlin development clients. Compare cross-tenant requests and the enforcement point.
Run local labDEMONIC BINARY / LABS
Explore runnable code, browser simulations and research on API authorization, sessions, release reliability and threat analysis.
OPEN SOURCE / HANDS-ON LABS
LAB 01
An intentionally vulnerable and corrected Node.js API with SwiftUI and Kotlin development clients. Compare cross-tenant requests and the enforcement point.
Run local labLAB 02
Drive session expiry, revocation and replay decisions through a deterministic model. No live accounts or network attack surface.
Run browser modelLAB 03
Observe what the release decision looks like when evidence is missing, a verification step fails or rollback is required.
Run browser modelLAB 04
Compare unsafe and guarded object lookups, then test the resulting access-control decisions against fabricated records.
Review the codeLAB 05
Analyze fabricated endpoint events and Android declarations, including missed detections and false positives.
Open threat labBEYOND THE LAB
We review mobile applications, APIs and backend workflows under a defined security assessment scope. Start with the attack surface and the access controls that matter.
Explore security assessmentsAPI object authorization and tenant isolation
Session revocation, replay and token lifecycle
Release integrity and recovery paths
Threat analysis and incident investigation
A commercial review begins with written permission, a defined target and safe test boundaries—not with a public demo URL.
Discuss scope and authorization