| Audit | Project | Date | Chain | Critical findings |
|---|---|---|---|---|
| SynaBonk | SynaBonk | Repository or files, no deployed address | No open critical findings | |
| Litas | Litas | 1 address on Ethereum | No open critical findings | |
| Zenko Protocol | Zenko Protocol | Repository or files, no deployed address | No open critical findings | |
| Litmex protocol | Litmex protocol | Repository or files, no deployed address | No open critical findings | |
| LICKO | LICKO | 1 address on BNB Chain | No open critical findings | |
| Moo. | Moo.Army | 1 address on Ethereum | No open critical findings | |
| MeowIstanbul | MeowIstanbul | Repository or files, no deployed address | No open critical findings | |
| CRTAI | CRT AI Network | 1 address on BNB Chain | No open critical findings | |
| Kibb. | Kibb.ai | 1 address on Ethereum | No open critical findings | |
| VIETDOGE | VIETDOGE | 1 address on BNB Chain | No open critical findings |
The field is a word set on each project when it was added to Trustblock, by the audit firm in the publishing form or by Trustblock’s importer. It describes the project, not the audit. A project with several fields is counted in each, so the counts can add up to more than the 1777 projects reviewed. A field on fewer than 10 of these projects is shown without a number. Counted from Cyberscope’s projects on Trustblock, as of 10 Oct 2026.