Shrub security record
As of 3 Nov 2026, Shrub has 1 audit report on Trustblock, by CertiK, dated 29 Nov 2024. That report lists no open critical findings. It also holds 1 deployed contract on 1 chain.
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
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Shrub token | Security firm: CertiK | Date: | Scope: 1 address on Ethereum | No open critical findings | Open · skynet.certik.com |
Findings12
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 1 | 0 | 1 |
| Medium | 0 | 1 | 0 |
| Low | 0 | 9 | 0 |
HighCentralization Related RisksShrub token · CertiK · 29 Nov 2024Fixed
In the contract `Contract`, 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 set automated market maker pair, exclude accounts from fees, update the developer wallet address, update the maximum transaction amount, enable trading and swap, set the launch block number, disable transfer delay, update the buy fees, blacklist or whitelist an account, set early sell tax status, update maximum wallet amount, update sell fees with a safety check, update swap enabled status, exclude an address from max transaction amount, update the marketing wallet address, remove limits in effect, and update swap tokens amount.  In the contract `Ownable`, 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 renounce the ownership or transfer contract ownership.  ### Onchain Analysis As of November 29, 2024, the contract is deployed at [0x3b991130eaE3CcA364406D718DA22FA1C3E7C256](https://etherscan.io/address/0x3b991130eae3cca364406d718da22fa1c3e7c256), and its ownership has been renounced through the transaction [0xd387c226e6d70a827d9dd33bb70bf5980f9dd3a1af9e748c552acd9c1ff122e9](https://etherscan.io/tx/0xd387c226e6d70a827d9dd33bb70bf5980f9dd3a1af9e748c552acd9c1ff122e9).
Open the reportContracts1
| Address | Chain | Source code |
|---|---|---|
| 0x3b991130eae3cca364406d718da22fa1c3e7c256 | Chain: Ethereum | Source 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
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="shrub-token"></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