Raiders / Public security work
Public work.
Inspect the evidence.
Security testing for crypto applications across web interfaces, APIs, backend services, infrastructure and operational dependencies.
Selected audits, vulnerability research and security-framework contributions. Each entry links to the published record and Raiders’ role.
Professional background
Engineering context.
Security judgment.
Raiders brings 6+ years of security industry experience, including security engineering leadership and full-stack penetration testing for crypto projects.
- Work connects smart-contract assumptions with the applications, identities, infrastructure and release paths around them. An engagement starts with the assets and user journeys that need protecting, then agrees on the actual review boundary.
- Professional background describes Raiders’ experience. The linked records below show specific public contributions and report credits; each source establishes its own scope and attribution.
Primary sources
Explore the public record.
Published assessments, research and framework contributions, with the role and scope linked to each source.
Audit reports
Selected audit reports.
Each report identifies the assessed artifacts, review period, methodology and findings. Follow the original for the full scope.
Audit report
MetaMask Connect — public audit summary
Cyfrin’s published v2.0 summary credits Raiders as lead auditor, with an assisting auditor. The scoped work spans SDK, mobile and extension integrations and relay infrastructure.
Role: Credited lead auditor in Cyfrin’s published summary
Recorded scope
- SDK and wallet integrations
- Mobile and extension communication
- Relay infrastructure
Source: Cyfrin: MetaMask Connect public summary (PDF)
Audit report
Predict.fun Chainlink CRE integration — public audit summary
Cyfrin’s published v2.1 summary credits Jorge and Raiders as lead auditors. The reviewed integration includes Solidity adapters and TypeScript CRE workflows.
Role: Credited joint lead auditor in Cyfrin’s published summary
Recorded scope
- Solidity adapters
- TypeScript CRE workflows
- Integration boundaries
Source: Cyfrin: Predict.fun CRE integration public summary (PDF)
Audit report
unflat collaborative audit
A public Sherlock report names Raiders alongside 0x69 as Lead Security Experts. The examined repositories include mobile and fund-flow service components.
Role: Named Lead Security Expert in a collaborative audit
Recorded scope
- Mobile application
- Fund-flow services
- Authentication and local storage paths
Source: Sherlock: unflat collaborative audit report (PDF)
Contributions & disclosures
Specific work.
Visible attribution.
MITRE AADAPT — Supply Chain Compromise (ADT1195)
MITRE AADAPT lists Chirag Agrawal, Web3Sec.News, as a contributor to its Supply Chain Compromise technique. The entry describes manipulation of products and delivery paths, with context for the digital-asset ecosystem.
Role: Named contributor: Chirag Agrawal, Web3Sec.News
Recorded scope
- Supply-chain compromise
- Software distribution and delivery paths
- Digital-asset operational dependencies
Source: MITRE AADAPT: ADT1195 — Supply Chain Compromise
MITRE AADAPT — Software Dependencies and Development Tools (ADT1195.001)
MITRE AADAPT also lists Chirag Agrawal, Web3Sec.News, as a contributor to the subtechnique Compromise Software Dependencies and Development Tools. Its scope connects compromised development components with cryptocurrency software and operational systems.
Role: Named contributor: Chirag Agrawal, Web3Sec.News
Recorded scope
- Software dependencies and development tools
- Malicious changes to trusted components
- Wallet and digital-asset software supply chains
Source: MITRE AADAPT: ADT1195.001 — Compromise Software Dependencies and Development Tools
CVE-2022-4722: rdiffweb authentication bypass
Raiders’ public portfolio lists this research. The CVE record documents an authentication-bypass issue in rdiffweb before version 2.5.5.
Role: Research listed in Raiders’ public vulnerability portfolio
Recorded scope
- Authentication
- Web application security
Source: NVD: CVE-2022-4722
Research attribution: Raiders’ public research portfolio. The disclosure and research credit are linked separately.
CVE-2023-3067: Trilium stored cross-site scripting
Raiders’ public portfolio lists this research. The CVE record documents stored cross-site scripting in Trilium before version 0.59.4.
Role: First-person published vulnerability research
Recorded scope
- Stored cross-site scripting
- Application security
Source: NVD: CVE-2023-3067
Research attribution: Raiders’ published research write-up. The disclosure and research credit are linked separately.
SEAL Domain & DNS Security framework
SEAL’s framework overview credits Raiders as an author, connecting domain and DNS controls to the infrastructure behind applications.
Role: Named author on the published framework overview
Recorded scope
- Domain and registrar controls
- DNS security
- Infrastructure dependencies
Source: SEAL: Domain & DNS Security overview
DNS monitoring, alerts and incident response
A second SEAL chapter credits Raiders for material on DNS change detection, alerting and response responsibilities.
Role: Named author on the published chapter
Recorded scope
- DNS change monitoring
- Alert ownership
- Incident response preparation
Source: SEAL: Monitoring, Alerts, and Incident Response
Community participation
ETHSecurity Badge holder
TheDAO Security Fund
Selected for TheDAO Security Fund’s ETHSecurity Badge in April 2026. The program recognizes researchers who help secure Ethereum and participate in decisions about security funding.
Selection announcement ↗About the badge program ↗Selection process ↗
Funded public goods
Ethereum security public goods
Web3Sec.News and DigiBastion have both received Ethereum-security public-goods funding through TheDAO Security Fund. Its transparency record lists both projects as funded recipients.
TheDAO Security Fund support
Web3Sec.News: Security Intelligence & Newsletter
Security intelligence, research and education
Public-goods security research and newsletter work for the Ethereum ecosystem.
View the fund’s recipient record ↗TheDAO Security Fund support
DigiBastion: DNS, OpSec & Supply Chain Security
Domain, operational and supply-chain security
A public-goods initiative focused on the infrastructure and operational dependencies around crypto applications.
View the fund’s recipient record ↗This support relates to the named public-goods projects. Commercial security reviews have their own agreed scope and deliverables.
Context and boundaries
Read the attribution.
Keep the scope.
- Public links document the named work, role and scope. A collaborative report credit describes that contribution; it does not imply sole authorship, current employment by the publisher or endorsement of every Web3Sec service.
- Framework contributor credits describe the published contribution, not employment, certification or endorsement of Web3Sec services by the framework publisher.
- A report covers its stated artifacts and review period. Later releases and fixes require their own review. Confidential engagements are not turned into public case studies without authorization.
For the reporting method, inspect the clearly fictional finding walkthrough. That teaching specimen is separate from the original public work linked on this page.
Your system, its own scope
Bring the architecture.
Define the question.
A public artifact can help you assess how someone works. Your engagement still needs its own agreed system boundary, evidence, deliverables and decision owner.
Application security
Web, API & full-stack pentesting
Explore authorization, business logic, identity and the boundaries between application components.
Scope an application review →Protocol security
Smart contract security audits
Examine protocol assumptions, permissions, accounting and the interactions that move value.
Scope a contract review →Agree on the work
Inputs, outputs & boundaries
Compare engagement shapes and prepare the context needed for a useful first conversation.
Compare the engagement →