Security, with a wider lens.
A contract. An API. An agent with production access.
The risk rarely stops where the code does.
Web3Sec brings technical security work, incident research, and business perspective together — led by Raiders.
Independent thinking. Evidence before claims.
The important question often lives
between the components.
Smart contracts / Applications / AI systems / People & operations
The research desk
Source-linked investigations and security notes. Read the evidence, follow the failure, take the useful lesson.
All research →Recent framework advisories connect upstream libraries, image processing, caching and cookie handling to the software actually running in production.
Read the noteThe February 2025 theft shows why multiple signatures cannot compensate for a shared, compromised view of a transaction.
Read the noteA package-publishing compromise reached applications through dynamically loaded code without changing their own repositories.
Read the noteA curated library, not a live alert feed. How we research and publish ↗
Ways to work together
Focused engagements around the decisions you need to make. Clear scope, documented evidence, and a path from findings to fixes.
Challenge the assumptions, permissions, and economic edge cases in the code that moves value.
Follow the attack paths between identities, application workflows, APIs, and the systems they can reach.
Prepare the decisions, access, and evidence your team will need when normal assumptions stop holding.
Examine what your agents can act on, what your build trusts, and how untrusted input can reach a privileged action.
Turn complex engineering and security work into material that readers can understand, inspect, and use.
Connect security priorities, product decisions, and a technical story that stands up to scrutiny.
Follow the boundaries between the mobile app, the device, external entry points and the APIs that authorize real actions.
Field guides
Practical references for reviewing systems, preparing for incidents, and strengthening how you ship.
Open the guide library →An operating procedure for the accounts that control email, cloud infrastructure, source code and company recovery.
Separate mailbox compromise, domain spoofing and support impersonation into controls with observable tests.
A runbook for registrar ownership, scoped DNS changes, renewal resilience and safe nameserver recovery.
I’m Raiders. Web3Sec is where technical security, thoughtful communication, and the realities of building a company meet.
More about Raiders →A good place to start
A launch, an architecture decision, a suspicious signal, or something that needs explaining. Let’s define the work it needs.