Exohood Labs emblem EXOSWAP
SECURITY / PUBLIC RECORDS
EXO TOKEN · HISTORICAL SECURITY REVIEWS

Security isn't a claim.
It's a record.

Explore the published EXO smart contract audit reports, understand their scope, and verify the findings directly with the original sources. Transparent security means showing both the work done and the limits of that work.

TWO PUBLISHED REPORTS ETHEREUM + BNB CHAIN INDEPENDENT SOURCES
REVIEW RECORDEXO / SECURITY
Exoswap robot assistant
CONTRACT SCOPE
SOURCE LINKED
ANIMATED VISUALIZATION · NOT A LIVE SECURITY SCAN
PUBLIC REPORTS2Published repository references
EARLIEST REVIEW2021Intercer Iberia · BEP-20
LATEST LISTED REVIEW2024Cyberscope · ERC-20
REFERENCE SCOPEEXOToken contracts, not the whole app
001 / VERIFIED REFERENCES

Published audit reports.

Two independently attributed smart contract security reviews appear in the public EXO audit repository. Open the original files to read each auditor's methodology, scope, observations and recommendations.

INDEPENDENT SMART CONTRACT REVIEW

Cyberscope

2024
MAIN TOKEN / ERC-20
REVIEW DATE30 January 2024
BLOCKCHAINEthereum

Cyberscope reviewed the EXO Ethereum smart contract. The external security page provides a findings breakdown and published contract reference. Findings should be read alongside the full report and their remediation status.

PUBLIC LISTING FINDINGS*
0 critical1 medium9 minor10 unresolved
ERC-20 CONTRACT
0xbd8005612124DC30601E22D8B5d188A89767c640

*Findings shown in the public Cyberscope listing at review. Refer to the source for current values and interpretation.

INDEPENDENT SMART CONTRACT REVIEW

Intercer Iberia SL

2021
EXO TOKEN / BEP-20
REPOSITORY DATE11 November 2021
BLOCKCHAINBNB Chain

The public repository identifies an earlier smart contract audit attributed to Intercer Iberia SL, associated with the EXO BEP-20 contract. The original document is available for reviewing the historical assessment and its limitations.

The repository confirms the report and date; no separate live finding count is asserted here.
BEP-20 CONTRACT
0x7D10B6157C7C577CAa62D319dC215209Cf2dB8C3

The date and auditor attribution follow the project's published repository index.

Original audit repository

Browse the published documents and their change history directly on GitHub.

Open repository
002 / HOW TO READ A REPORT

Findings, not marketing.

An audit is a time-specific examination of selected code. The findings can help readers distinguish immediate vulnerabilities, design risks and lower-severity issues from broader product claims.

CYBERSCOPE / PUBLIC RECORDETH / 2024
CRITICAL0
MEDIUM1
MINOR9

10 unresolved findings were listed in the third-party audit profile when checked. A count by itself does not explain exploitability, impact, mitigation or current contract permissions.

Examine the live security breakdown

Critical / high severity

Issues that could enable serious loss or compromise and usually require immediate review. A zero count does not prove that no vulnerability exists.

Medium severity

Material weaknesses that may matter in specific conditions, contract states or combinations of actions.

Minor / informational

Lower-severity findings may involve design consistency, coding practices, event handling or maintainability. They still deserve scrutiny.

Unresolved doesn't mean safe

Always check whether an item was fixed, acknowledged, mitigated or left outstanding. Read the actual report rather than a score alone.

003 / PRACTICAL VERIFICATION

Verify before you trust.

Reports are useful when their scope can be tied to the exact contracts and versions in use. A visitor should be able to follow that evidence without relying on a badge.

01

Open the original

Read the source report, its audit date, the auditor attribution and any scope or limitations stated in the document.

02

Match the contract

Compare the blockchain, deployed address and code version with what the report actually examined.

03

Review the findings

Check the severity, real impact, recommended fixes and any independent evidence of remediation.

04

Check current controls

Audit findings are historical. Verify live permissions, contract updates, network activity and third-party dependencies.

004 / SECURITY SCOPE

What these reports do not establish.

These public reports relate to specific EXO token smart contracts and the code reviewed at the time. They do not, by themselves, establish that the entire current Exoswap interface, swap routing, 0x integration, bridges, WalletConnect flows, third-party pools, website infrastructure or Polygon deployment has undergone the same independent audit.

Smart contract audits cannot eliminate phishing, price volatility, front-end compromise, wallet risk or changes in third-party protocols. Users should verify current addresses and independently assess transaction risk.

EXO token
005 / AUDIT HISTORY

A visible timeline.

These dates come from the published GitHub repository index. They document historical assessments, not an assurance of continuous review.

21
11 NOVEMBER 2021

Intercer Iberia SL · EXO BEP-20

Historical smart contract audit reference for the BNB Chain deployment, published in the project's report repository.

View 2021 report
24
30 JANUARY 2024

Cyberscope · EXO ERC-20

Ethereum token contract audit documented in the repository, with a public Cyberscope security page that includes a finding classification.

View 2024 report
006 / SECURITY KNOWLEDGE

Audit questions, answered.

Security reviews are valuable evidence, but they are not a substitute for understanding what was tested and what remains outside the assessed scope.

Does an audit make EXO or Exoswap risk free? +

No. An audit evaluates selected code and risks at a particular time. It cannot eliminate every vulnerability or guarantee market value, liquidity, wallet security or uninterrupted service.

Which EXO networks are referenced? +

The repository identifies Cyberscope for the Ethereum ERC-20 contract and Intercer Iberia SL for the BNB Chain BEP-20 contract. The listed documents do not establish a separate Polygon audit.

Does the Cyberscope listing show zero problems? +

No. Its public profile reported no critical findings but did list a medium finding, minor findings and unresolved items. Read the complete published report and current finding status.

Are swap and bridge contracts covered by these reports? +

These sources concern the EXO token smart contracts. They should not be interpreted as audits of the current 0x-based routing, external bridges, all third-party liquidity sources or the entire web interface.

Why does the contract address matter? +

Multiple contracts can share a token name or symbol. Verify the deployed chain and the exact address to see whether the report actually applies to the code you are considering.

Where can I disclose a security issue? +

Use the Help Center to contact the Exoswap support team. Do not publish seed phrases, private keys or other confidential credentials in a public message.

TRANSPARENCY IS ONGOING

Verify the source.
Understand the risk.

Read the full reports, inspect the audited contracts and make informed decisions. No third-party security review constitutes a guarantee of safety or future performance.

View complete audit archive