- Home
- Security Audits
- CryptoBatz
Web3 · Smart Contract Audit
CryptoBatz Security Audits
softstack has completed 2 smart contract audits for CryptoBatz in January 2022, reporting 5 findings in total (2 low and 3 informational), of which 3 were resolved or mitigated before the final reports. Every report is published in the softstack public audit archive.
Key facts
- Client
- CryptoBatz
- Audits completed
- 2
- Latest audit
- Chains
- Ethereum
- Languages
- Solidity
About the project
CryptoBatz is an Ethereum NFT collection of 9,666 bat characters created by Ozzy Osbourne together with the studio Sutter Systems. Each bat can bite an NFT from a selected partner collection once, producing a derivative MutantBat that combines traits from both tokens. The collection launched in 2022 and its published roadmap is marked complete.
Findings
Combined across all 2 reviews softstack has completed for CryptoBatz. Each report is broken out below.
3 of 5 findings resolved before the final reports.
Reports
Newest first. Every report covers its own scope and commit.
by Ozzy Osbourne smart contract audit
0Critical0High0Medium2Low3Informational3 of 5 resolved
Scope
Components reviewed
1 module · 1 file- CryptoBatz.sol
All 5 findings
ID Title Severity Status 5.1.1Missing zero-address check Code Snippet Result/Recommendation In the current implementation, there are several addresses set without checking for the zero address. This can lead to unintended behaviour.
Low acknowledged 5.1.2Spelling and Grammatical Errors Code Snippet Result/Recommendation Spelling and grammatical errors were identified in the codebase.
Low fixed 5.1.3A floating pragma is set Code Snippet Result/Recommendation The current pragma Solidity directive is "^0.7.5". It is recommended to specify a fixed compiler version to Line 1: pragma solidity ^0.8.8; It is recommended to follow the latter example, as future…
Informational fixed 5.1.4State variable could be declared constant Code Snippet Result/Recommendation In the current implementation are constant variables not defined as constants.
Informational acknowledged 5.1.5Storing data via baseURI Code Snippet Result/Recommendation In the current implementation the baseURI is not hardcoded or on-chain generated, means the owner/creator is free to choose the way how the metadata file is stored.
Informational fixed Mutantbatz smart contract audit
Severity breakdown is in the published report.
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 auditsMethodology
Review process
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.
Automated analysis
Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.
Manual code review
Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.
Adversarial testing
Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.
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.
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
CryptoBatz 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 has completed 2 smart contract audits for CryptoBatz in January 2022. The published reports are linked on this page and in the softstack public audit archive.
2 separate reviews. Each one covers its own scope and commit, and is listed individually on this page.
5 findings across all 2 reviews: 2 low and 3 informational. 3 of 5 were resolved or mitigated before the final reports.
Each report covers the code as it stood at the commit it names, the most recent in January 2022. Any code changed after that point is outside the reviewed scope.
Related audits
Browse all security auditsDisclaimer
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.