Avabot audit reports

Avalancheavabot.co

Avabot has 1 public audit report from Paladin; dated 29 Jan 2024; no critical findings reported. It also holds 4 deployed contracts on 1 chain.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm12

Statuses are the security firms’ own

12 findings are still open or acknowledged in the firms’ reports: 2 high, 10 low (1 open, 11 acknowledged).

High
2
Low
10
  • High Open

    delegatecall allows all approvals to be stolen

    Audit Report · Paladin · 29 Jan 2024 · Report ↗

  • High Acknowledged

    Aggregated governance issues

    Audit Report · Paladin · 29 Jan 2024 · Report ↗

  • Low Acknowledged

    Custom tokens might allow for reentrancy within certain calls

    Audit Report · Paladin · 29 Jan 2024 · Report ↗

  • Low Acknowledged

    feesData address can block swap

    Audit Report · Paladin · 29 Jan 2024 · Report ↗

  • Low Acknowledged

    Integer division within receive function will result in minimal dust

    Audit Report · Paladin · 29 Jan 2024 · Report ↗

  • Low Acknowledged

    Lack of granularity for fee determination

    Audit Report · Paladin · 29 Jan 2024 · Report ↗

  • Low Acknowledged

    Lack of slippage check within swap

    Audit Report · Paladin · 29 Jan 2024 · Report ↗

  • Low Acknowledged

    Low granularity for percentage distribution

    Audit Report · Paladin · 29 Jan 2024 · Report ↗

  • Low Acknowledged

    Malicious addresses might result in DoS due to revert upon fee receipt

    Audit Report · Paladin · 29 Jan 2024 · Report ↗

  • Low Acknowledged

    Multi-hop swaps might revert due to max tx check

    Audit Report · Paladin · 29 Jan 2024 · Report ↗

All 12 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Audit ReportSecurity firm: PaladinDate: Scope: 4 addresses on AvalancheNone openFindings: 3 high · 5 medium · 17 low
13 fixed · 11 acknowledged · 1 open
paladinsec.co ↗

Findings25

Statuses are the security firm’s own, from each report.

SeverityOpenAcknowledgedFixed
Critical000
High111
Medium005
Low0107
Highdelegatecall allows all approvals to be stolenAudit Report · Paladin · 29 Jan 2024Open

The report gives no description here.

Open the report

Contracts4

AddressChainSource code
0xbdbe51b4206a7677039c1b7b9d6b0e31159c9c99Chain: AvalancheSource code: Verified source
0x27b0ddb09157171316089ebafbe5e7dff8979c5eChain: AvalancheSource code: Verified source
0x2ff23cf639c18ad49e50e89e10f0b59f147788b0Chain: AvalancheSource code: Verified source
0x9f71b3118d97a448b127bf7677a59ab7454d0a04Chain: AvalancheSource code: Verified source

Avabot: questions

Is Avabot audited?

Trustblock holds 1 public audit report for Avabot, dated 29 Jan 2024. The latest is by Paladin (“Audit Report”).

Who audited Avabot?

Paladin wrote the report Trustblock holds for Avabot.

Are there open findings in Avabot’s audits?

12 findings are still open or acknowledged in the firms’ reports: 2 high, 10 low (1 open, 11 acknowledged). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

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.

Content

Facts

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.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="avabot"
></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