Welthee security record
As of 25 Oct 2026, Welthee has 1 audit report on Trustblock, by CertiK, dated 6 Sep 2022. That report lists no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Audits1
Newest first
Findings6
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 1 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 1 |
| Low | 0 | 0 | 4 |
CriticalCentralization Risks in InsuredTokenSale.solWelthee · CertiK · 6 Sep 2022Fixed
In the contract `InsuredTokenSale` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and withdraw all the tokens owned by the contract from any `ERC20` contract, then transfer these funds from the `_owner` account to their own account. 
Open the reportMediumNo Tokens Transferred To The ContractWelthee · CertiK · 6 Sep 2022Fixed
The linked functions attempt to transfer `ERC20` tokens out of this contract to EOA's and vesting contracts. This contract never explicitly receives tokens and as a result, it will most likely revert during balance checks and token transfers.
Open the reportLowMissing Emit EventsWelthee · CertiK · 6 Sep 2022Fixed
There should always be events emitted in the sensitive functions that are controlled by centralization roles.
Open the reportLowPotential Cross-chain Replay AttackWelthee · CertiK · 6 Sep 2022Fixed
Within the current contract, there is no distinction between the different blockchains supported by the `Welthee` project. If the signer signed a message on one chain (e.g. Ethereum), and accidentally leaks the message, the message would be valid for a similar transaction of a chain with the same encryption method (e.g. BSC). For example, if the signer signed a message using `encodeClaimHash(ClaimParam memory claimInfo)` on Ethereum and the same `claimInfo.investor` and `claimInfo.id` exists on BSC, the attacker can reuse this signed message to maliciously claim tokens with `claim()` on BSC.
Open the reportLowUnhandled Expiry Time CaseWelthee · CertiK · 6 Sep 2022Fixed
Neither of the `if` statements in the function `isAvailableToClaim()` check whether `orders[investor][id].insuranceExpiryTime` is equal to `block.timestamp`. The order will have neither a claim type of `INSURANCE` nor `TOKEN` in this case even if the order has not been claimed before.
Open the reportLowUnused ContractWelthee · CertiK · 6 Sep 2022Fixed
```solidity=4 library AddressesArray { ``` - The library `AddressesArray` is included in the audit scope but is never used by the other contracts.
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="welthee"></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