As of 3 Nov 2026, IRIS Network has 2 audit reports by 1 security firm on Trustblock; the latest is by CertiK, dated 1 Mar 2024. Those reports list 1 open critical finding. 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.
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| BEP20 Contract for IRISnet Token (IRIS) | Security firm: CertiK | Date: | Scope: 1 address on BNB Chain | No open critical findings | Open · skynet.certik.com |
| ICS-721 Implementation (Golang) | Security firm: CertiK | Date: | Scope: Files named in the report | 1 open critical finding | Open · skynet.certik.com |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 1 | 0 | 0 |
| High | 1 | 2 | 0 |
| Medium | 0 | 2 | 0 |
| Low | 13 | 0 | 6 |
Files: - `nft-transfer/keeper/relay.go` Commits: - [`cfc058309adcf73478d3828a524ecf8e546420ed`](https://github.com/bianjieai/nft-transfer/tree/cfc058309adcf73478d3828a524ecf8e546420ed) - [`87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba`](https://github.com/bianjieai/nft-transfer/tree/87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba) - [`fa7bd3f3cb1ebe24f781953a781add96509b4c2a`](https://github.com/bianjieai/nft-transfer/tree/fa7bd3f3cb1ebe24f781953a781add96509b4c2a) The function `Transfer()` is used to transfer the NFT, which it accepts the classID and tokenID to uniquely identify the NFT. Additionally, it specifies the `tokenData` that is an app specific data of the NFT if it is available. ```go Transfer(ctx sdk.Context, classID string, tokenID string, tokenData string, receiver sdk.AccAddress) error ``` However, when invoking the `Transfer()`, the functions, `createOutgoingPacket()` and `refundPacketToken()` provide empty `tokenData` instead of the `tokenData` associated with the NFT.
Open the reportFiles: - `ibc_module.go` Commits: - [`cfc058309adcf73478d3828a524ecf8e546420ed`](https://github.com/bianjieai/nft-transfer/tree/cfc058309adcf73478d3828a524ecf8e546420ed) - [`87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba`](https://github.com/bianjieai/nft-transfer/tree/87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba) - [`fa7bd3f3cb1ebe24f781953a781add96509b4c2a`](https://github.com/bianjieai/nft-transfer/tree/fa7bd3f3cb1ebe24f781953a781add96509b4c2a) When handling acknowledgement packet in function `OnAcknowledgementPacket()`, event is triggered with type of `EventTypePacket`. An attribute with key of `AttributeKeyAckSuccess` is emitted first along with other attributes in the new event. After that, a new event is emitted that depends on the acknowledgement response type: ```go=243 switch resp := ack.Response.(type) { case *channeltypes.Acknowledgement_Result: ctx.EventManager().EmitEvent( sdk.NewEvent( types.EventTypePacket, sdk.NewAttribute(types.AttributeKeyAckSuccess, string(resp.Result)), ), ) ``` The same `AttributeKeyAckSuccess` is set but with different values. Hence, there will cause confusion in the following event tracking.
Open the reportFiles: - `nft-transfer/types/trace.go` Commits: - [`cfc058309adcf73478d3828a524ecf8e546420ed`](https://github.com/bianjieai/nft-transfer/tree/cfc058309adcf73478d3828a524ecf8e546420ed) - [`87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba`](https://github.com/bianjieai/nft-transfer/tree/87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba) - [`fa7bd3f3cb1ebe24f781953a781add96509b4c2a`](https://github.com/bianjieai/nft-transfer/tree/fa7bd3f3cb1ebe24f781953a781add96509b4c2a) The function `ParseHexHash()` is used to parse the hex hash in string format to bytes and validates its correctness. ```go=18 func ParseHexHash(hexHash string) (tmbytes.HexBytes, error) { hash, err := hex.DecodeString(hexHash) if err != nil { return nil, err } if err := tmtypes.ValidateHash(hash); err != nil { return nil, err } return hash, nil } ``` However, an empty string could by converted to empty bytes, which may result in errors or unexpected behavior.
Open the reportFiles: - `go.mod` Commits: - [`cfc058309adcf73478d3828a524ecf8e546420ed`](https://github.com/bianjieai/nft-transfer/tree/cfc058309adcf73478d3828a524ecf8e546420ed) - [`87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba`](https://github.com/bianjieai/nft-transfer/tree/87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba) The callback of `OnRecvPacket` is implemented in the upper module for the `RecvPacket` message, which is in the ibc core modules. This is imported by the go module file as a dependency, i.e. > github.com/cosmos/ibc-go/v6 v6.1.0 > github.com/cosmos/ibc-go/v5 v5.0.1 However, as published in the security advisory, the ibc-go with version `v6.1.0` and `v5.0.1` contain thee huckleberry vulnerability and the fix was reflected in the commit [`4973957900d70969d99371e6ed24c47400f5abe6`](https://github.com/cosmos/ibc-go/commit/4973957900d70969d99371e6ed24c47400f5abe6?ref=jumpcrypto.com) and patch was released in the following versions: - v7.0.1 - v6.1.1 - v5.3.1 - v5.2.1 It breaks the core assumptions of off-chain components that rely on the events listening, and can lead to a wide range of unexpected security vulnerabilities in various products. Moreover, the cosmos-sdk versions used in the following commits should be updated according to the barberry security advisory: - [`cfc058309adcf73478d3828a524ecf8e546420ed`](https://github.com/bianjieai/nft-transfer/tree/cfc058309adcf73478d3828a524ecf8e546420ed) - [`87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba`](https://github.com/bianjieai/nft-transfer/tree/87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba) **Reference** - https://forum.cosmos.network/t/ibc-security-advisory-huckleberry/10731 - https://forum.cosmos.network/t/cosmos-sdk-security-advisory-barberry/10825
Open the reportFiles: - `keeper/grpc_query.go` - `types/trace.go` Commits: - [`cfc058309adcf73478d3828a524ecf8e546420ed`](https://github.com/bianjieai/nft-transfer/tree/cfc058309adcf73478d3828a524ecf8e546420ed) - [`87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba`](https://github.com/bianjieai/nft-transfer/tree/87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba) - [`fa7bd3f3cb1ebe24f781953a781add96509b4c2a`](https://github.com/bianjieai/nft-transfer/tree/fa7bd3f3cb1ebe24f781953a781add96509b4c2a) The function `ParseHexHash()` is intended to parse a hex hash in string format to bytes and validate its correctness. **types/trace.go** ```go=18 func ParseHexHash(hexHash string) (tmbytes.HexBytes, error) { hash, err := hex.DecodeString(hexHash) if err != nil { return nil, err } if err := tmtypes.ValidateHash(hash); err != nil { return nil, err } return hash, nil } ``` If any error occurs, the returned variable `hash` is nil, which will be used in the error message of function `ClassTrace()`. **keeper/grpc_query.go** ```go=28 hash, err := types.ParseHexHash(strings.TrimPrefix(req.Hash, "ibc/")) if err != nil { return nil, status.Error(codes.InvalidArgument, fmt.Sprintf("invalid denom trace hash: %s, error: %s", hash.String(), err)) } ``` As a result, an empty string will be passed in the error message.
Open the reportFiles: - `nft-transfer/types/codec.go` Commits: - [`cfc058309adcf73478d3828a524ecf8e546420ed`](https://github.com/bianjieai/nft-transfer/tree/cfc058309adcf73478d3828a524ecf8e546420ed) - [`87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba`](https://github.com/bianjieai/nft-transfer/tree/87cdf3b7dd969237c9ffc8e056bfc24cab5e2bba) - [`fa7bd3f3cb1ebe24f781953a781add96509b4c2a`](https://github.com/bianjieai/nft-transfer/tree/fa7bd3f3cb1ebe24f781953a781add96509b4c2a) In file `codec.go`, the `MsgUpdateParams` has not been registered as a concrete implementation of the interface `sdk.Msg`, which could lead to an error when being marshalled or unmarshalled.
Open the report| Address | Chain | Source code |
|---|---|---|
| 0x05c5…f6f70x05c50a62b0b87be1ffb1cf3b77d9edba834ef6f7 | Chain: BNB Chain | Source code: Verified source |
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.
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.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="iris-network"></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