Anoma security record

As of 21 Oct 2026, Anoma has 2 audit reports by 2 security firms on Trustblock; the latest is by Nethermind Security, dated 13 Nov 2025. Those reports list 1 critical acknowledged and not fixed.

Critical findings
1 critical acknowledged, not fixed
Reported in “Namada Ethereum Bridge audit” by Oak Security, Mar 2023. The team acknowledged it. See the findings
Open the latest report
Your label, live
Get the label for your site

Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.

Audits2

Newest first

AuditSecurity firmDateScopeCritical findingsReport
Anoma security reviewSecurity firm: Nethermind SecurityDate: Scope: Not recorded (see the report)No open critical findingsOpen · GitHub
Namada Ethereum Bridge auditSecurity firm: Oak SecurityDate: Scope: Not recorded (see the report)1 critical acknowledged, not fixedOpen · GitHub

Findings15

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

SeverityOpenAcknowledgedFixed
Critical011
High014
Medium000
Low017

Marked Info, Best Practices or Informational by the firms. Not counted as findings.

InfoDifferences between the specification and implementationAnoma security review · Nethermind Security · 13 Nov 2025Acknowledged

The report gives no description here.

Open the report
InfoPrivacy Leakage through imageID usageAnoma security review · Nethermind Security · 13 Nov 2025Acknowledged

The report gives no description here.

Open the report
InformationalInclude a check to ensure that a transfer is sent only if the slashed_amount is greater than 0Namada Ethereum Bridge audit · Oak Security · 28 Mar 2023Acknowledged

The report gives no description here.

Open the report
InformationalInstance of potential integer overflow on arithmetic operationsNamada Ethereum Bridge audit · Oak Security · 28 Mar 2023Acknowledged

The report gives no description here.

Open the report
Best PracticesRemove debug trait for secret keyAnoma security review · Nethermind Security · 13 Nov 2025Fixed

The report gives no description here.

Open the report
Best PracticesShould constrain logic instances’ length to match the number of keys in the batch circuitAnoma security review · Nethermind Security · 13 Nov 2025Fixed

The report gives no description here.

Open the report
InfoThe function verifyMerkleProof() does not distinguish between the leaves and nodesAnoma security review · Nethermind Security · 13 Nov 2025Fixed

The report gives no description here.

Open the report
InformationalLess than half of the available wrapped transactions from the mempool are potentially included in a proposalNamada Ethereum Bridge audit · Oak Security · 28 Mar 2023Fixed

The report gives no description here.

Open the report
InformationalTypographical errorNamada Ethereum Bridge audit · Oak Security · 28 Mar 2023Fixed

The report gives no description here.

Open the report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

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="anoma"
></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