Web3 · Smart Contract Audit

BABB Security Audit

softstack completed a smart contract audit of BABB's BAX Token in May 2022, reporting 15 findings (2 high, 3 medium, 7 low and 3 informational). The full report is published in the softstack public audit archive.

Key facts

Client
BABB
Completed
Chains
Ethereum
Languages
Solidity, JavaScript
Market cap
$504,527 as of 2026-09-30

About the project

BABB operates Babb, a hybrid account that combines a GBP balance with cryptocurrency in a single mobile app. Account holders can deposit, withdraw, send and convert between pounds and crypto, with GBP funds safeguarded as e-money. The company positions the product for people underserved by conventional banks, and its BAX token is issued on Ethereum.

Scope

Components reviewed

3 modules · 3 files
  1. BAX_Token.sol
  2. truffle-config.js
  3. hardhat.config.js

Findings

0Critical
2High
3Medium
7Low
3Informational

0 of 15 findings resolved before the final report.

IDTitleSeverityStatus
6.2.1Owner Can Burn Any User Funds

After blacklisting a user, the owner is able to burn funds from the user.

Highacknowledged
6.2.2Owner Can Freeze User Funds

The contract owner can blacklist a user at any time. Afterwards the selected user funds are frozen, they are able to be transferred.

Highacknowledged
6.2.3Outdated Compiler Version

The used compiler version ^0.4.17 was released in September 2017 and is deprecated. The current solidity compiler version is 0.8.13.

Mediumacknowledged
6.2.4Unexplicit Types

In the current implementation unexplicit types of unsigned integer variables are used.

Mediumacknowledged
6.2.5Replacement Of Contract Logic

The logic of the underlying token contract can be replaced by the owner at any time. This replacement can be unaudited malicious code and implement various attack vectors, if the owner wallet is breached / hacked.

Mediumacknowledged
6.2.6Wrong Import Of OpenZeppelin Library

In the current implementation, OpenZeppelinfiles are added directly into the code. This violates OpenZeppelin’s MIT license, which requires the license and copyright notice to be included

Lowacknowledged
6.2.7Deprecated Use Of Constant

The “constant” keyword on functions is deprecated and was removed on 0.5.0. It is an alias for the newer view keyword.

Lowacknowledged
6.2.8Missing OwnershipTransferred Event

The current implementation of ownable library is missing the OwnershipTransferred event, which is normally emitted on transferring ownership.

Lowacknowledged
6.2.9Use Require Messages

The current implementation is not providing any feedback on failing actions.

Lowacknowledged
6.2.10Deprecated Var Keyword

The unexplicit var keyword has been deprecated for security reasons in 0.4.20 and should not be used anymore.

Lowacknowledged
6.2.11Redundant Function

In the current implementation are redundant functions to get the owner of the BlackList.

Lowacknowledged
6.2.12Unlimited Minting To Max Cap

In the current implementation the owner is able to mint new tokens at any time until the max cap is reached.

Lowacknowledged
6.2.13Floating Pragma Version Identified

It is recommended to specify a fixed compiler version to ensure that the bytecode produced does not vary between builds. This is especially important if you rely

Informationalacknowledged
6.2.14Improper Use Of Interfaces

In the current implementation contract keyword is used for interfaces.

Informationalacknowledged
6.2.15Variable Usage Before Definition

In the current implementation a variable is used before it was defined.

Informationalacknowledged

About this engagement

A smart contract audit reviews on-chain code for flaws an attacker could exploit. Engineers trace how assets move through the contracts, check who can call privileged functions, and test the arithmetic, external calls and upgrade paths. Each finding is rated by severity, and fixes are re-checked before the final report.

How softstack runs smart contract audits

Methodology

Review process

  1. Scoping and threat modelling

    The commit hash is frozen and the attack surface is mapped: asset flows, trust assumptions, privileged roles and the external systems the code depends on.

  2. Automated analysis

    Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.

  3. Manual code review

    Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.

  4. Adversarial testing

    Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.

  5. Reporting

    Every finding is documented with a severity rating, its impact, the steps to reproduce it and a concrete remediation the team can act on.

  6. Remediation verification

    Submitted fixes are re-reviewed against the original finding, and the final report records the resolved state of each one.

Standards and references

  • SWC RegistrySmart Contract Weakness Classification
  • CWECommon Weakness Enumeration

FAQ

BABB was audited by softstack GmbH, a German Web3 security and software company based in Flensburg and certified to ISO/IEC 27001 by TÜV SÜD. softstack completed a smart contract audit for BABB in May 2022. The full report is linked on this page and published in the softstack public audit archive.

The review reported 15 findings: 2 high, 3 medium, 7 low and 3 informational. 0 of 15 were resolved or mitigated before the final report.

3 source files were reviewed. The published report lists every file covered.

This report covers the code as reviewed in May 2022. Any code changed after that point is outside the reviewed scope.

Related audits

Browse all security audits

Disclaimer

This audit represents a point-in-time security assessment of the reviewed codebase and is intended for informational purposes only. While Softstack applies industry-standard security review methodologies, no audit can guarantee the absence of vulnerabilities, bugs, or other security risks. This report does not constitute financial, legal, regulatory, or investment advice, nor does it endorse the project, its business model, products, or services. Security is an ongoing process, and we strongly recommend conducting a new assessment following any material code changes or at least every 6 months to address newly emerging threats, vulnerabilities, and ecosystem developments.