Xsurge security record

BNB Chainxsurge.net

As of 24 Oct 2026, Xsurge has 4 audit reports by 2 security firms on Trustblock; the latest is by SolidProof, dated 12 May 2022. Those reports list no open critical findings. It also holds 3 deployed contracts on 1 chain and 1 incident (latest 15 Aug 2021).

Critical findings
No open critical findings
Across 4 reports.
Incident
Incident 15 Aug 2021
Source: De.Fi incident database. 4 audits have been published since. See the incident
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.

Audits4

Newest first

AuditSecurity firmDateScopeCritical findingsReport
XsurgeSecurity firm: SolidProofDate: Scope: 1 address on BNB ChainNo open critical findingsOpen · IPFS
XsurgeSecurity firm: SolidProofDate: Scope: 1 address on BNB ChainNo open critical findingsOpen · IPFS
XSURGESecurity firm: SolidProofDate: Scope: Not recorded (see the report)No open critical findingsOpen · IPFS
SurgeUselessSecurity firm: CertiKDate: Scope: 1 address on BNB ChainNo open critical findingsOpen · skynet.certik.com

Findings25

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

SeverityOpenAcknowledgedFixed
Critical000
High010
Medium000
Low2220
HighCentralization Related RisksSurgeUseless · CertiK · 24 Feb 2022Acknowledged

In the contract `SurgeUSELESS`, the role `owner` has the authority over the following function: - function ActivateSurgeToken() - function enableEmergencyMode() - function setAllowSurgeStaking(bool allow) - function updateFundingValues(bool allowSurgeFunding, uint256 transferDenom, uint256 buySellDenom) - function updateSurgeFundAddress(address newSurgeFund) - function setIsApprovedLP(address LP, bool isLP) - function updateUseOfUselessBypass(bool useBypass) - function changeGarbageCollectorThreshold(uint256 garbageThreshold) - function transferOwnership(address newOwner) - function renounceOwnership() Any compromise to the `owner` account may allow the hacker to manipulate the project through these functions.

Open the report
LowFinance ModelSurgeUseless · CertiK · 24 Feb 2022Acknowledged

The SurgeUseless Protocol is a decentralized deflation token deployed on the Binance smart chain (BSC). The user can stake USELESS and BNB to obtain SUSLS. When the user transfers BNB into the contract, the contract will burn all the balance of SUSLS in the contract when the balance reaches `garbageCollectorThreshold`. The price of SUSLS = the USELESS balance of the contract / the total supply of SUSLS. When the user stakes/sells SUSLS, the transaction will charge 6% of the amount of SUSLS as the fee. When the user transfers SUSLS, the transaction will charge 4% of the amount of SUSLS as the fee. If `allowFunding` is true, some of the fees will be given to `_surgeFund`, and the remaining will be burned. It should be noted that whether it is the purchase, sale or transaction, the exchange ratio between USELESS and SUSLS will change. If the operation charges the fee, the price of SUSLS will rise, and the price of SUSLS will remain unchanged if no fee is charged.

Open the report
LowThird Party DependenciesSurgeUseless · CertiK · 24 Feb 2022Acknowledged

The contract is serving as the underlying entity to interact with third-party UselessSwapper protocols. The scope of the audit treats 3rd party entities as black boxes and assumes their functional correctness. However, in the real world, 3rd parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of 3rd parties can possibly create severe impacts, such as increasing fees of 3rd parties, migrating to new LP pools, etc.

Open the report

Incidents1

Attached through a shared contract address. Our incident data ends in Oct 2026.

Incident

Incident,

com/tx/0x7e2a6ec08464e8e0118368cb933dc64ed9ce36445ecf9c49cacb970ea78531d2 The hacker made a flash loan of 10,000 BNB and purchased 202 trillion SURGEs, next sell() 202 trillion SURGEs within reentrancy to purchase(), where the price is calculated before updating _totalSupply to a smaller one, thus gaining more SURGEs.

Source: De.Fi incident database.

Audits before it
0.
Audits since
4, the latest dated 12 May 2022.

Contracts3

AddressChainSource code
0x2e62e57d1d36517d4b0f329490ac1b78139967c0Chain: BNB ChainSource code: Verified source
0xf1394748c3163813de6617662dabac36b35d4407Chain: BNB ChainSource code: Verified source
0x1bc2abdb4190d6006ccf21724508477820a72dc8Chain: BNB ChainSource code: Verified source

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