Rip.fun has 2 public audit reports from Pashov Audit Group; the latest is Pashov Audit Group, 17 May 2025; 2 critical findings, all marked fixed by the firms.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
15 findings are still open or acknowledged in the firms’ reports: 15 low (all acknowledged).
Incorrect packet burning mechanism in bundle allocation
Rip It · Pashov Audit Group · 17 May 2025 · Report ↗
requestConfirmations below Chainlink minimum allowed in UpdateVRFConfig()
Rip It · Pashov Audit Group · 17 May 2025 · Report ↗
Revocation may fail after currency update allowing exploits
Rip It · Pashov Audit Group · 17 May 2025 · Report ↗
Data inconsistency risk from modifying critical addresses in cardAllocationPool
Rip It · Pashov Audit Group · 2 May 2025 · Report ↗
Data integrity issue with revertBurnRequest in RipFunPacks
Rip It · Pashov Audit Group · 2 May 2025 · Report ↗
Inconsistent prize locking/unlocking from dynamic weight changes
Rip It · Pashov Audit Group · 2 May 2025 · Report ↗
Inconsistent role ID in cardAllocationPool initialization
Rip It · Pashov Audit Group · 2 May 2025 · Report ↗
Inconsistent validation in isValidListing() and isValidTrade()
Rip It · Pashov Audit Group · 2 May 2025 · Report ↗
Insufficient error handling
Rip It · Pashov Audit Group · 2 May 2025 · Report ↗
No duplicate prize check in prize pool addition
Rip It · Pashov Audit Group · 2 May 2025 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| Rip It | Security firm: Pashov Audit Group | Date: | Scope: —Not recorded; see the report | 2 critical findings, fixed | Findings: 2 critical · 2 high · 2 medium · 21 low 24 fixed · 3 acknowledged | GitHub ↗ |
| Rip It | Security firm: Pashov Audit Group | Date: | Scope: —Not recorded; see the report | None open | Findings: 7 high · 14 medium · 33 low 42 fixed · 12 acknowledged | GitHub ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 2 |
| High | 0 | 0 | 9 |
| Medium | 0 | 0 | 16 |
| Low | 0 | 15 | 39 |
The reports name a repository or files. Open a report to see its scope.
Trustblock holds 2 public audit reports for Rip.fun, dated 2 May 2025 to 17 May 2025. The latest is by Pashov Audit Group (“Rip It”).
Pashov Audit Group wrote the 2 reports Trustblock holds for Rip.fun.
15 findings are still open or acknowledged in the firms’ reports: 15 low (all acknowledged). Of 2 critical findings: all marked fixed by the firms. Statuses are the security firms’ own.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="ripfun"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us