About / The person behind the work

Raiders.
Security across the stack.

I’m Raiders. I bring 6+ years of security industry experience, including security engineering leadership and full-stack penetration testing for crypto projects.

Raiders / Leading Web3Sec

From code to company.

Security testing for crypto applications across web interfaces, APIs, backend services, infrastructure and operational dependencies.

I approach security as a question about how a real system behaves: who can act, what they can affect, what the system depends on, and what happens when those assumptions fail. Code matters. So do the people who deploy it, the interface someone signs through, the credentials a build can access, and the way a team responds when something unexpected happens.

Web3Sec connects that perspective across focused technical reviews, crypto operational security, web, API and mobile pentesting, incident readiness, AI and supply-chain security, technical writing, and security advisory. Each engagement has an agreed technical boundary, authorized access, concrete deliverables and a clear route from findings to remediation.

My aim is to make complicated security questions easier to act on without flattening their technical meaning. The work should leave engineers with evidence they can inspect and decision-makers with a clear explanation of the consequences, tradeoffs, and next steps.

Public work includes a named Lead Security Expert credit in a Sherlock collaborative audit, CVE research, credited lead-auditor roles in Cyfrin’s published MetaMask Connect and Predict.fun summaries, and authorship credits in SEAL’s Domain & DNS Security framework.

MITRE AADAPT lists my contributions under “Chirag Agrawal, Web3Sec.News” on its supply-chain compromise and software-dependency technique pages.

I’m also an ETHSecurity Badge holder with TheDAO Security Fund. My selection announcement ↗ · About the program ↗

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. View TheDAO’s funding record ↗

What Web3Sec is becoming

A place for useful work
and inspectable ideas.

01 / Practice

Work with the actual system.

Start with the architecture, the behavior, and the decision the team needs to make. Agree on the right review depth, inputs, outputs, and boundaries before work begins.

Explore the services →
02 / Research

Learn from how things fail.

The public library connects sourced incident reports and technical mechanisms to practical lessons. It distinguishes original investigation findings from Web3Sec’s own interpretation.

Read the research →
03 / Judgment

Show what supports the conclusion.

Use tools to deepen the work, keep claims proportional to the evidence, and make uncertainty explicit. A useful recommendation should make the next decision clearer.

Read the approach →

How I want the work to feel

Direct, thoughtful,
and grounded.

A finding should explain how a failure becomes possible and what would address it. A technical article should help its reader understand a mechanism or make a decision. An advisory conversation should end with a clearer question, a concrete choice, or a next step with an owner.

That means being willing to disagree, revise an interpretation when evidence changes, and identify where another specialist is needed. It also means respecting the difference between client work and public writing. Confidential material is not automatically a portfolio piece, and commercial relationships should not determine editorial conclusions.

If that sounds like the way you want to work, share a little context about your system and what you are trying to resolve. Keep the first message high level; we can agree on confidentiality and a private channel before exchanging source code or sensitive evidence.

Start a conversation →

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.