CertiK reviewed Probinex (Probinex - New Deal) on 3 Nov 2022: 4 findings, 0 critical; none marked fixed.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 2 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 2 | 0 | 0 |
In the contract `PbxToken` the role `BLACKLISTER_ROLE` has authority over the functions shown in the diagram below. Any compromise to the `BLACKLISTER_ROLE` account may allow the hacker to take advantage of this authority and 1) Blacklist all the users with `DEFAULT_ADMIN_ROLE`, rendering them useless, by preventing them from calling the `grantRoleString()` and `revokeRoleString()` functions. It would become impossible to revoke the `BLACKLISTER_ROLE` from the hacker, if this were to happen. 2) Blacklist the users with `PAUSER_ROLE`, rendering them useless, and making it impossible to call the `pause()` function that disables the transfer of tokens and `unpause()` function that enables the transfer of tokens. 3) Blacklist the users using the `blacklist()` function that prevents them from participating in transfer of tokens and prevents the user with `DEFAULT_ADMIN_ROLE` to assign any new roles to them. 4) Allow the blacklisted users to participate in transfer of tokens using the `unBlacklist()` function.  In the contract `PbxToken` the role `PAUSER_ROLE` has authority over the functions shown in the diagram below. Any compromise to the `PAUSER_ROLE` account may allow the hacker to take advantage of this authority and 1) Disable the transfer of tokens using the `pause()` function. 2) Enable the transfer of token using the `unpause()` function.  In the contract `PbxToken` the role `SNAPSHOT_ROLE` has authority over the functions shown in the diagram below. Any compromise to the `SNAPSHOT_ROLE` account may allow the hacker to take advantage of this authority to hold tokens as short a time as possible to be included in each snapshot.  In the contract `PbxToken` the role `DEFAULT_ADMIN_ROLE` has authority over the functions shown in the diagram below. Any compromise to the `DEFAULT_ADMIN_ROLE` account may allow the hacker to take advantage of this authority and grant `PAUSER_ROLE`, `SNAPSHOT_ROLE` and `BLACKLISTER_ROLE` to users, or revoke them using `grantRoleString()` and `revokeRoleString()` functions. 
All the tokens are sent to the `_msgSender()` when deploying the contract and no further minting of the tokens is possible. This could be a centralization risk as the deployer of the contract can distribute these tokens without obtaining the consensus of the community.
Literals with many digits are difficult to read and review.
1) The `_mint()` function is called only in the constructor where no user is blacklisted. The modifiers `notBlacklisted(account)` and `notBlacklisted(_msgSender())` in the definition of `_mint()` function will always return true. 2) The `_mint()` function has the following require statement to put a cap on the total number of tokens in the contract but the parent contract `ERC20Capped` already takes care of it so, it can be removed. ```solidity=123 require( ERC20.totalSupply() + amount <= cap(), "ERC20Capped: cap exceeded" ); ``` 3) The contract does not allow minting of new tokens after construction. The inheritance of `ERC20Capped` contract can be avoided since the tokens in the contract are never going to increase after the minting of `CAP` amount of tokens during deployment.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (1)
1,045 projects reviewed · 1,376 reports · latest May 2025
See CertiK’s auditsSomething 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