1dayexploit
Our story

We are a security research community.

1dayexploit is a research hub - not a vendor, not a consultancy, nothing to sell. A group of researchers that reads vulnerabilities down to the source, builds the tooling to do it, and gives all of it away.

We exist because of a gap. Most published vulnerabilities are a paragraph of prose and a severity score: whether the thing actually works, what it takes to make it work, and whether the fix really closes it are all left to the reader. We work the 1-day window - the interval between a patch landing and widespread exploitation, when defenders are racing to deploy and attackers are racing to reverse-engineer. A CVE is a claim. We turn claims into evidence.

What we do

Three things.

  • Read. We take a disclosed vulnerability apart - the patch diff, the source, the conditions it actually needs - and publish the analysis in full.
  • Find. We hunt for new flaws ourselves and work with whoever maintains the software to get them closed. What we report is published as an advisory once there is a fix, never before.
  • Build. Doing the first two by hand does not scale, so we write the tooling that makes it repeatable - and release it instead of keeping the advantage.
How we work

Evidence over assertion.

A finding is only published once it has been demonstrated. Our engine ÂLIM rebuilds a vulnerability in an isolated containerised lab, develops a working proof-of-concept, and runs it against both the vulnerable and the patched build - so the fix is verified, not assumed.

We also say plainly when something could not be reproduced, or only partly worked. A failed analysis is a result too, and hiding it would make everything else we publish worth less.

Tooling

We build what we needed and did not have.

ÂLIM is the engine behind all of it. It reads the public CVE feed as it lands, works out which of the three hundred thousand entries are reproducible at all, and ranks those by how exposed and how exploitable they actually are - so the queue is decided by evidence rather than by whichever CVE got a headline.

It is free to use and open to requests: anyone can point it at a CVE from the public dashboard and we publish what comes back. No account, no quota.

What we publish

Proof, or nothing.

You will find here:

  • Root cause analyses of recently disclosed vulnerabilities, traced through the source
  • Patch diffs read line by line, and reverse engineering walkthroughs
  • Proof-of-concept exploits, released post-patch
  • Our own security advisories when we disclose a finding

You will not find:

  • Unpatched zero-days, or anything for sale
  • Novice-level content or commodity exploit walkthroughs
Repositories

Everything we produce is free.

No product, no paywall, no lead capture. Analyses, write-ups and proof-of-concept code are published openly.

Disclosure policy

Patch first.

We do not sell vulnerabilities, share them with third parties, or publish exploits before a patch is available. Everything is released for research and educational use. We do not endorse or assist unauthorized use.

We give our work back to the databases, maintainers and researchers whose work we build on. Corrections to anything we have published are welcome and credited.