- Home
- Security Audits
- WhIsBe
Web3 · Smart Contract Audit
WhIsBe Security Audit
softstack completed a smart contract audit of WhIsBe's Long Lost Friends WhIsBe Vandalz in July 2022, reporting 8 findings (3 medium, 1 low and 4 informational), of which 1 was resolved or mitigated before the final report. The full report is published in the softstack public audit archive.
Key facts
- Client
- WhIsBe
- Completed
- Chains
- Ethereum
- Languages
- Solidity, JavaScript
- Commit
2f3259b49490
About the project
WhIsBe is an NFT project built around Vandalz, a collection of 11,111 animated 3D characters on Ethereum that carry a narrative of innocence lost. The WhIsBeVerse ties the collection to physical items and community access. Earlier WhIsBe collectibles, including Good Karma Tokens and Karma Keys, can be swapped for Vandalz, though automated contract redemption has closed.
Scope
Source repositorygithub.com/Aegis-Studio-Dev/whisbe-vandalzComponents reviewed
6 modules · 6 files- ERC721RandomlyAssignVandalzTier.sol
- ERC721RandomlyAssignVandalzTierPeriphery.sol
- WhisbeVandalz.sol
- GoodKarmaToken.sol
- truffle-config.js
- hardhat.config.js
Findings
1 of 8 findings resolved before the final report.
| ID | Title | Severity | Status |
|---|---|---|---|
6.2.1 | Predictable Random Number By using the blockhash and the block variable attributes, malicious users can predict the outcome of the random number generation. | Medium | fixed |
6.2.2 | Centralization Risk The Owner has the rights to mint token, set baseURI and pause mint / redemption. This represents a significant centralization risk, where the Owner has too much control over the contract. | Medium | acknowledged |
6.2.3 | Unlimited Mint The creatorMint and mintEmergencySupply function allows the Owner to mint new tokens to a specific address. If this function is not used carefully, it can cause inflation of the tokens. | Medium | acknowledged |
6.2.4 | Missing Value Verification Certain functions lack a value safety check, the values of the arguments should be verified to allow only the ones that comply with the contract’s logic. | Low | acknowledged |
6.2.5 | Floating 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 | Informational | acknowledged |
6.2.6 | Missing Natspec Documentation Solidity contracts can use a special form of comments to provide rich documentation for function, return variables, and more. This special form is named Ethereum Natural Language Specification Format (NatSpec). | Informational | acknowledged |
6.2.7 | Missing Error Message Require statements check if a condition is true and allow code to flow only if the condition is true. If the condition is false, require will throw an error, the rest of the code will not be executed and the transaction will revert. | Informational | acknowledged |
6.2.8 | Storing Data Via baseURI 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 | acknowledged |
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
WhIsBe 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 WhIsBe in July 2022. The full report is linked on this page and published in the softstack public audit archive.
The review reported 8 findings: 3 medium, 1 low and 4 informational. 1 of 8 were resolved or mitigated before the final report.
6 source files were reviewed in github.com/Aegis-Studio-Dev/whisbe-vandalz at commit 2f3259b. The published report lists every file covered.
This report covers the code as reviewed in July 2022 at commit 2f3259b. 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.