A centralized archive documenting a persistent exploitation model within the Google VRP. Includes evidence logs, verified backend status flags, and chronological timelines detailing the discrepancy between external 'infeasible' status closures and internal verification of high-impact reports.
This repository documents a systemic pattern of VRP negligence observed during the 2026 cycle. It serves as a single source of truth for researchers who have received "infeasible" status on verified, high-impact findings.
Evidence suggests a "string-out strategy" where reports are subjected to artificial triage delays to facilitate internal reverse engineering, followed by silent production patches and ticket closure under false pretenses.
| Date | Event | VRP Status |
|---|---|---|
| March 26, 2026 | Submission of P1 exploit chain | P1 Verified (Internal) |
| May 8, 2026 | Report closure | "Infeasible" |
| May 11, 2026 | Related patch/write-up published | N/A |
- Backend Verification: See
/evidence/backend_flags/for screenshots confirming "P1_verified_by_mckay" status. - Communication Logs: See
/evidence/comms/for correspondence demonstrating the shift from active engagement to arbitrary dismissal.
This repository remains active to provide the data that was suppressed in the official portal. The timeline speaks for itself.