Skip to content

SECURITY RESEARCH / TECHNICAL ANALYSIS

From weakness to engineering action.

Original attack-path analysis, security test models and incident investigations focused on mobile, backend and AI boundaries.

ORIGINAL RESEARCH / PUBLIC ENGINEERING WORK

Security notes and reproducible investigations.

01 / API / ACCESS CONTROL

API Object Authorization: A Cross-Tenant Access Test

Examine how an authenticated request can cross a tenant boundary if a backend uses an object identifier without checking ownership. Run the local test and compare the fix.

Engineering takeaway

Reproduce an unauthorized object request, enforce the tenant check in the backend and rerun negative-path tests.

Open the lab

02 / MOBILE / DEVICE TRUST

Native Client Integrity and Server-Side Authorization

Trace how mobile integrity signals, session state and sensitive-data access cross the iOS/Android and backend boundary.

Engineering takeaway

Differentiate device-integrity evidence from authorization. Review token validation and per-request permission checks.

Read the test matrix

03 / AI AGENTS / TOOL SECURITY

AI Agent Tool Invocation as an Authorization Boundary

Explore prompt-injection and unsafe-action paths where a model can request a tool operation but should not decide execution permissions.

Engineering takeaway

Bind actions to authenticated identity, resource scope and approval policy; test replay, retries and prompt manipulation.

Try the authorization model

04 / PRODUCTION / ROUTING

Cloudflare Worker Redirect Loop and Recovery

A first-party incident investigation into canonical host redirects, static asset lookups, 404 behavior and safer route handling.

Engineering takeaway

Trace the original redirect cycle and inspect the corrected routing path and current negative-route behavior.

Read the incident report

COORDINATED DISCLOSURE

Found a vulnerability affecting us?

Use the responsible reporting channel for security issues affecting Demonic Binary. For third-party products, contact the relevant vendor and follow their disclosure process.

Report a Vulnerability

Research, not speculation

We describe test conditions and reference the code or record behind each technical note.

Safe testing only

Public labs use authorized systems and synthetic fixtures.

Coordinated publication

Third-party findings are published through an appropriate disclosure process.