Polygon security record

As of 29 Oct 2026, Polygon has 12 audit reports by 6 security firms on Trustblock; the latest is by ChainSecurity, dated 8 May 2025. Those reports list no open critical findings. It also holds 2 deployed contracts on 1 chain.

Critical findings
No open critical findings
Across the 12 reports, 6 critical findings were reported. Each is marked fixed by the firm that reported 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.

Audits12

Newest first

AuditSecurity firmDateScopeCritical findingsReport
Vault Bridge TokenSecurity firm: ChainSecurityDate: Scope: Files named in the reportNo open critical findingsOpen · chainsecurity.com
POL Transition Smart ContractsSecurity firm: ChainSecurityDate: Scope: Files named in the report1 critical finding, fixedOpen · chainsecurity.com
Polygon security reviewSecurity firm: Sigma PrimeDate: Scope: Not recorded (see the report)No open critical findingsOpen · GitHub
Polygon Token (POL) Security Audit

Audit · firm’s term: security audit

Security firm: ChainSecurityDate: Scope: Files named in the reportNo open critical findingsOpen · chainsecurity.com
Polygonid security reviewSecurity firm: Nethermind SecurityDate: Scope: Not recorded (see the report)No open critical findingsOpen · GitHub
Polygon security reviewSecurity firm: Sigma PrimeDate: Scope: Not recorded (see the report)No open critical findingsOpen · GitHub
Polygon Technology security reviewSecurity firm: HexensDate: Scope: Not recorded (see the report)No open critical findingsOpen · GitHub
Polygon PoS PortalSecurity firm: ChainSecurityDate: Scope: Not recorded (see the report)No open critical findingsOpen · chainsecurity.com
Polygon ZkEVM security reviewSecurity firm: HexensDate: Scope: Not recorded (see the report)4 critical findings, fixedOpen · GitHub
Polygon Fx PortalSecurity firm: ChainSecurityDate: Scope: Not recorded (see the report)No open critical findingsOpen · chainsecurity.com
Audit ReportSecurity firm: PaladinDate: Scope: 2 addresses on Polygon (POS)No open critical findingsOpen · paladinsec.co
MaticSecurity firm: CertiKDate: Scope: Files named in the report1 critical finding, fixedOpen · skynet.certik.com

Findings95

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

SeverityOpenAcknowledgedFixed
Critical006
High006
Medium1510
Low1957
MediumUse (Up to Date) DependenciesPolygon Fx Portal · ChainSecurity · 14 Dec 2022Open

The report gives no description here.

Open the report
LowInefficient comparisonMatic · CertiK · 19 Apr 2021Open

In function `numItems()` by the definition of `RLPItem` it is clear the the value of `currPtr` can never exceed `endPtr` and the while loop on line 234 would stop when `currPtr` and `endPtr` are equal, hence instead of `currPtr < endPtr` we can use `CurrPtr != endPtr` as each not equal comparison costs 3 less gas (negligible for short `RLPItem`, this exhibit is just here for completeness) than less than comparison

Open the report

Contracts2

AddressChainSource code
0xa9de045d9e8b619ed12fc4947f10d371621de492Chain: Polygon (POS)Source code: Verified source
0xd9d2114c8ea72298d5748f9684b4aadfec6731a3Chain: Polygon (POS)Source code: Verified source

All 2 addresses and the files the reports name

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