| IF-IBC-01 | Refund logic differs between code and specification | Specification deviation | Medium | Spec |
| IF-IBC-02 | Faulty semantics underspecified | Unclear Specification | Medium | Spec |
| IF-IBC-03 | Incorrect Properties | Specification error | High | Spec |
| IF-IBC-04 | Relayer underspecified | Unclear specification | Low | Spec |
| IF-IBC-05 | Suggestions for ICS 02 Restructuring | Specification restructuring proposal | Informative | Spec |
| IF-IBC-06 | Token lost issue in the crossing hellos scenario | Specification error | High | Spec |
| IF-IBC-07 | Type mismatch | Specification deviation | Low | Spec |
| IF-IBC-08 | Wrong usage of unbonding period | Protocol Bug | Medium | Code |
| IF-IBC-09 | Malicious IBC app module can claim any port or channel capability | Implementation Bug | High | Code |
| IF-IBC-10 | Escrow address collisions | Protocol / Implementation Bug | High | Code |
| IF-IBC-11 | Crossing hellos with fixed identifier are not live | Protocol / Implementation Bug | Medium | Code |
| IF-IBC-12 | Non-atomicity of operations | Bad Software Practice / Lack of Documentation | Informative | Code |
| IF-IBC-13 | Model-based Testing for Token Transfer | Set of new artifacts to facilitate rigorous testing | Informative | Code |
| IF-IBC-14 | Panic on receiving multi-chain denominations | Implementation Bug | High | Code |