Parex security record
As of 3 Nov 2026, Parex has 1 audit report on Trustblock, by CertiK, dated 15 Oct 2024. That report lists no open critical findings.
Record last updated . It holds audits, findings and contracts up to Nov 2026, and incidents up to Oct 2026. Trustblock does not review code.
Audits1
Newest first
Findings14
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 1 |
| High | 0 | 1 | 4 |
| Medium | 0 | 0 | 2 |
| Low | 0 | 3 | 3 |
HighCentralization Risks in PRX-BSCToken.solParex · CertiK · 15 Oct 2024Acknowledged
In the contract `BSCToken`, the role `PRX` has authority over the functions shown in the diagram below. Any compromise to the `PRX` account may allow the hacker to take advantage of this authority. - `pause()`: pause the contract - `unpause()`: unpause the contract - `blacklist()`: add a account to blacklist - `unblacklist()`: remove a account from blacklist - `unlockTokens()`: unlock the tokens - `setBridgeFee()`: set the `bridgeFee` - `setMaxAmount()`: set the `maxAmount` - `sendBridgeOwnerReward()`: withdraw the token 
Open the reportLowFixed Fee Deduction in `unlockTokens` FunctionParex · CertiK · 15 Oct 2024Acknowledged
The `unlockTokens()` function, called by the contract owner to unlock tokens for users, deducts a fixed `bridgeFee` instead of a fee proportional to the amount of tokens being unlocked. This introduces a potential inconsistency in the amount of tokens unlocked for users, especially in cases where larger token amounts are involved. ```solidity=145 if (amount > 0) { require(amount > bridgeFee, "Amount must be greater than bridge fee"); amountToMint -= bridgeFee; // Deduct the bridge fee bridgeTotalFee += bridgeFee; // Accumulate the total fees collected } ```
Open the reportLowPull-Over-Push Pattern In `transferOwnership()` FParex · CertiK · 15 Oct 2024Acknowledged
The change of `_owner` by function `transferOwnership()` overrides the previously set `_owner` with the new one without guaranteeing the new `_owner` is able to actuate transactions on-chain.
Open the reportLowWithout Re-Approving in `_burnFrom` FunctionParex · CertiK · 15 Oct 2024Acknowledged
The `_burnFrom` function allows users to burn tokens without updating their allowance. Specifically, on line 798, the function checks the user's approved allowance but does not to reduce the allowance after execution. This allows users to repeatedly call the function without re-approving the contract. ```solidity=797 function _burnFrom(address account, uint256 amount) internal virtual { uint256 currentAllowance = allowance(account, address(this)); require(currentAllowance >= amount, "ERC20: burn amount exceeds allowance"); _burn(account, amount); } ```
Open the reportContracts
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
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.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="parex"></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