$300 awarded on Fireblocks MPC Managed Bug Bounty Engagement, against github.com/fireblocks/mpc-lib.
Everything Bugcrowd published about this
- Programme
- Fireblocks MPC Managed Bug Bounty Engagement In our directory, so it has reviews and a grade.
- Platform handle
- fireblocks-mbb-og2
- Asset
- github.com/fireblocks/mpc-lib The specific asset the finding landed against, as the platform named it.
- Severity
- low Bugcrowd rates P1–P5; this is that rating in HackerOne's words so the two feeds can sit in one table.
- Award
- $300 What the platform printed. Where a report carried more than one payment they are summed.
- Found by
- ShahzaibKhanzada Named because the finder allowed the platform to name them.
- State
- unresolved — accepted, not yet fixed
- Accepted
- 21 July 2026 2 months ago. This is the date the programme accepted the finding.
- First seen here
- 16 August 2026 When our sweep first read this entry. It says nothing about the finding, only about us.
- Platform reference
- 9fe5a0b8-497d-4834-921d-9f997f025d50
Where this award sits
A single large number tells you nothing on its own. What matters is whether this programme pays like this routinely or whether this was the one time it did.
It is the 3rd largest of 3 awards this programme has published. It sits below this programme's median, so larger figures are routine here.
Every figure here is drawn only from awards a platform chose to publish, which is a minority of what gets paid. Read the median as "of the payouts made public", never as "what this programme pays".
The only finding we hold from ShahzaibKhanzada
This is the only published finding we hold from ShahzaibKhanzada on Bugcrowd. That is a statement about our coverage, not about their record: we read a few pages of each feed per sweep, and most accepted work is never published at all.
Counted within Bugcrowd only. The same handle on another platform may or may not be the same person, and this page will not assume it is.
What else Fireblocks MPC Managed Bug Bounty Engagement has published
- github.com/fireblocks/mpc-lib low · resolved · withheld · 2 months ago —
- github.com/fireblocks/mpc-lib low · resolved · syybsam · 3 months ago —
- github.com/fireblocks/mpc-lib low · unresolved · db89 · 3 months ago —
- github.com/fireblocks/mpc-lib low · resolved · withheld · 4 months ago —
- github.com/fireblocks/mpc-lib medium · resolved · AccurateBenni89633 · 4 months ago $10,000
- github.com/fireblocks/mpc-lib low · resolved · adilburak · 4 months ago —
- github.com/fireblocks/mpc-lib low · resolved · MuhammadSharieff561e062-e6d3-4843-8419-33aa0a20483d · 4 months ago —
- Finding accepted low · resolved · MuhammadSharieff561e062-e6d3-4843-8419-33aa0a20483d · 4 months ago —
See Fireblocks MPC Managed Bug Bounty Engagement's grade and researcher reviews →
Where this came from. One row of a public platform feed, stored as published and never edited. We hold no report title, no write-up and no reproduction steps, because the feeds do not carry them and we do not go looking for them. A withheld name stays withheld; if a finder later asks the platform to un-name them, the next sweep un-names them here. Absence of an award figure is publication policy, not evidence a programme did not pay.