Public audit record
MetaMask Connect — public audit summary
Credited lead auditor in Cyfrin’s published summary
Read the published source ↗Security, with a wider lens.
Look closer.
Question the
assumptions.
A contract. An API. An agent with production access.
The risk rarely stops where the code does.
Security testing, crypto OpSec, incident readiness and technical advisory — led by Raiders.
Independent security. Clear decisions.
WEB3SEC / DEPENDENCY STUDY01
From protocol to production
Smart contracts / Applications / AI systems / People & operations
Selected public work
Reports you can
inspect.
Published audit records credit Raiders on specific work. Follow the source for the role, scope and review period.
Public audit record
Predict.fun Chainlink CRE integration — public audit summary
Credited joint lead auditor in Cyfrin’s published summary
Read the published source ↗Public audit record
unflat collaborative audit
Named Lead Security Expert in a collaborative audit
Read the published source ↗Reports, CVE research, MITRE AADAPT and SEAL contributions →
The research desk
What failed.
What to change.
Source-linked investigations and security notes. Read the evidence, follow the failure, take the useful lesson.
All research →RESEARCH NOTESWeb2
Next.js October and November 2026 advisories: patch the deployed artifact
Recent framework advisories connect upstream libraries, image processing, caching and cookie handling to the software actually running in production.
Read the noteRESEARCH NOTESWeb3
Bybit and Safe: the signing interface is part of your security boundary
The February 2025 theft shows why multiple signatures cannot compensate for a shared, compromised view of a transaction.
Read the noteRESEARCH NOTESSupply chain
Ledger Connect Kit: offboarding and runtime dependencies share a security boundary
A 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
Technical depth.
Practical judgment.
Focused engagements around the decisions you need to make. Clear scope, documented evidence, and a path from findings to fixes.
Protect the operation.
Review signing, privileged access and the incident decisions around the people and systems that move value.
Test the product.
Examine smart contracts, applications, APIs and mobile clients against the behavior they should enforce.
Make the work dependable.
Bound automation and software delivery, make security decisions explicit, and communicate the technical evidence clearly.
Field guides
For the work
in front of you.
Practical references for reviewing systems, preparing for incidents, and strengthening how you ship.
Open the guide library →01
Identity
02Identity security: phishing-resistant login, usable recovery and verified offboarding
An operating procedure for the accounts that control email, cloud infrastructure, source code and company recovery.
Email
03Email security: protect the recovery inbox and control who can send as your domain
Separate mailbox compromise, domain spoofing and support impersonation into controls with observable tests.
Domains & DNS
Domain and DNS security: preserve control of the address your users trust
A runbook for registrar ownership, scoped DNS changes, renewal resilience and safe nameserver recovery.
A note from Raiders
Good security work should
leave you with better questions.
And a way to answer them.
Raiders brings 6+ years of security industry experience, including security engineering leadership and full-stack penetration testing for crypto projects.
A good place to start
Bring the difficult
security question.
A launch, an architecture decision, a suspicious signal, or something that needs explaining. Let’s define the work it needs.