Immunefi
Case study

Alchemix

Alchemix keeps 89% of reports off its team, and its bug bounty still caught a critical

89% of reports closed by triage before reaching the team, in the 12 months to October 2026

Hundreds of hours of engineering time saved, in Alchemix's words

About 3 hours from a critical report to Alchemix's team

Case study01/ 06

At a glance

  • Client: Alchemix, a self-repaying loans protocol, on Immunefi since 2021
  • Challenge: from 2022 to 2024, about 7 in 10 bug reports went straight to the engineering team, and only about 1 in 7 of those was valid
  • What Immunefi does: runs the bug bounty, with the highest level of Managed Triage in front of Alchemix's team
  • Result: a critical in V3 reached the team about 3 hours after it was reported, and 89% of reports were closed before reaching the team in the 12 months to October 2026

Case study02/ 06

A critical bug in live V3 code

In June 2026, a researcher reported a critical in one of V3's vault strategies, a bug that put user funds at risk of theft. Immunefi's triage escalated it to Alchemix about 3 hours later. Alchemix confirmed it about 2 weeks later and paid the researcher in July, at the program's top reward at the time, nearly $300,000.

V3 had been through 5 security reviews before the bug was found. Each review checked the code on the day it ran, while user deposits sat in that code every day after, and the bug bounty keeps researchers looking at it for as long as it holds funds.

Case study03/ 06

The client

Alchemix offers self-repaying loans. Users borrow against a deposit, and the yield on that deposit pays the loan back. Its bug bounty has run on Immunefi since 2021. Alchemix launched V3 in April 2026, after an Immunefi audit competition, and runs a new bug bounty program for it.

Case study04/ 06

The challenge

From 2022 to 2024, about 7 in 10 reports went straight to Alchemix's team, and only about 1 in 7 of those was valid. Each invalid report still took an engineer's time to read, check and answer. While Alchemix built V3, it still had to keep V2 secure, and early in that period reports came in so often that one developer worked on triage full time.

“The triaging and mediation is night and day compared to a few years ago.”
Ov3rKoalafied, COO, Alchemix

Case study05/ 06

What changed

Before triage, a submission filter decides who can report at all, keeping out accounts with no track record and most bots. Researchers it blocked who then sent reports to Alchemix outside the platform have never had a valid bug.

Both of Alchemix's programs, V2 and V3, run on the highest level of Managed Triage, so Alchemix's engineers no longer read every report. The process behind that level has changed since the V2 program started, and today triage removes spam, duplicates and out-of-scope reports, then checks each remaining report against Alchemix's code, known issues and documentation, verifies the claimed impact, runs the proof of concept where it can and proposes a severity. A report that reaches the team arrives as a brief an engineer can act on.

Alchemix's team still decides which reports are valid, and Immunefi mediates when a researcher disputes a decision. Every report that triage closes stays visible to the team, so it can check triage's decisions at any time.

Case study06/ 06

The result

Ov3rKoalafied says the improved signal-to-noise on Immunefi freed up many more hours for V3 development and brought the launch forward by months. With V3 live, the team is building new products, and it no longer spends full weeks reviewing submissions, even as AI has pushed report volume up.

“Inherently you want to review every report, because of that voice in the back of your head of “what if it’s valid?”. Immunefi does an amazing job of looking at data across all their platforms to identify meaningful filtering methods so that you feel confident that what is submitted is worth reviewing, and even more importantly you feel confident that you don’t need to go review all the reports that were filtered out.”
Ov3rKoalafied, COO, Alchemix

In the 12 months to October 2026, 89% of the reports submitted to Alchemix were closed by Immunefi's triage before they reached the team. That figure counts only the reports that got past the submission filter. Of the reports that do reach the team, 1 in 4 is valid.

Source: Immunefi platform data for Alchemix's programs, October 17, 2025 to October 17, 2026. A report counts as reaching the team if it was escalated to Alchemix at any point.

“...their triaging services have saved us hundreds of hours... Immunefi helps keep the signal high and noise low.”
Alchemix team

Alchemix renewed in September 2026 for another year, on the same level of Managed Triage.

End of fileAlchemixCase study

When millions are at stake, who's finding your criticals matters

Talk to Immunefi about a bug bounty for your protocol.