GRUMPUS Info
$GRMPS is a utility token designed solely for use within the Grumpus ecosystem (GrumChat, GrumPad, GrumBuild, etc.). It is not intended as payment for goods or services outside this ecosystem, nor does it represent equity, ownership, dividends, voting rights, or any financial returns. The token’s value and liquidity are not guaranteed, and there is no obligation by the Company or Distributor to buy back or support secondary-market trading.
TrustNet Score
The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.
Real-Time Threat Detection
Real-time threat detection, powered by Cyvers.io,
is currently not
activated
for this project.
This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks.
For more information, click here.
Summary and Final Words
No crucial issues found
The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.
Contract owner cannot mint
It is not possible to mint new tokens.
Contract owner cannot blacklist addresses.
It is not possible to lock user funds by blacklisting addresses.
Contract cannot be locked
Owner cannot lock any user funds.
Token cannot be burned
There is no burning within the contract without any allowances
Ownership is not renounced
The owner retains significant control, which could potentially be used to modify key contract parameters.
Contract is not upgradeable
The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.
Scope of Work
This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.
The auditing process consists of the following systematic steps:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.
A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.
Final Words
The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.
Ownership Privileges
- The owner can set the sale token address.
- The owner can configure payable tokens and their price feeds.
- The owner can withdraw all sale tokens from the contract.
- The owner can rescue BNB from the contract.
- The owner can rescue any ERC20 tokens from the contract.
- The owner can set referral level rates.
- The owner can set the live stage ID.
- The owner can set the vesting start time.
- The owner can enable/disable claim functionality.
- The owner can enable/disable sale functionality.
- The owner can configure vesting parameters.
- The owner can whitelist/blacklist referrers.
- The owner can set a minimum buy amount.
Note - This Audit report consists of a security analysis of the GRUMPUS smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the GRUMPUS team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 2 findings
Resolved
#1 medium Issue
Missing nonReentrant check
The buyToken function performs external calls (token transfers via safeTransferFrom and ETH transfers via call) but lacks the nonReentrant modifier. This creates potential reentrancy vulnerabilities where malicious contracts could re-enter the function during external calls, potentially manipulating state variables or bypassing checks before state updates complete. Add nonReentrant modifier to buyToken function declaration: function buyToken(address _token, uint256 _amount, address _referrer) external payable nonReentrant saleEnabled.
Resolved
#2 medium Issue
Unlimited Referral Rate Setting Without Validation
The setLevelRate function lacks validation, allowing owner to set unlimited referral rates exceeding 100%. This could drain contract token supply through excessive referral distributions, create unfair tokenomics favoring referrers over purchasers, and potentially cause accounting errors in the presale system.
low Issues | 6 findings
Resolved
#1 low Issue
Missing Events
Critical admin functions lack events, preventing users from tracking important configuration changes like token settings, stages, and vesting parameters. Add emit statements for all critical onlyOwner configuration functions.
Resolved
#2 low Issue
Missing Zero Address Validation
The setTokenAddress() function doesn't validate that _saleToken is not the zero address. If a zero address is set, the contract will break when trying to call IERC20Metadata(saleToken). decimals () on line 735, and all token operations will fail. Add a zero address validation.
Resolved
#3 low Issue
Missing Validation for Referral Rate Limits
The function doesn't validate the referral rates in the _levelRate array. The owner could accidentally or maliciously set rates that exceed 100% (10000 basis points), causing the referral system to distribute more tokens than intended. This could drain the contract's token balance or cause accounting errors. Add validation for reasonable limits. Without validation, referral rates could be set to values that break the tokenomics and potentially drain the contract, making it a real financial risk.
Resolved
#4 low Issue
Missing Validation for Vesting Parameters
The setVestingInfo function lacks parameter validation, allowing owner to set vesting percentages exceeding 100% or zero cycle times. This could enable users to claim more tokens than purchased or cause division-by-zero errors in vesting calculations, potentially breaking the token distribution mechanism.
Resolved
#5 low Issue
Missing Maximum Threshold Validation in setMinimumBuy
The setMinimumBuy function lacks upper bound validation, allowing owner to set extremely high minimum purchase amounts that could effectively lock out all users from participating in the presale, making it inaccessible to regular investors and potentially restricting access to only whale participants. Add maximum threshold validation: require(minbuy <= reasonable_limit) to prevent setting unreasonably high minimum purchase amounts.
Resolved
#6 low Issue
Unnecessary SafeMath Usage
The contract uses SafeMath library with Solidity 0.8.25 which has built-in overflow/underflow protection. SafeMath adds unnecessary gas costs and code complexity since Solidity 0.8.0+ automatically reverts on arithmetic overflows/underflows, making the SafeMath library redundant and inefficient. Remove using SafeMath for uint256; and replace SafeMath function calls with native arithmetic operators.
optimization Issues | 1 findings
Pending
#1 optimization Issue
Code Quality/Design Flaw
The addStage() function lacks the onlyOwner modifier while other stage management functions like setLiveStageId() and editStage() are properly restricted. This inconsistency allows any user to create stages and increment the nextStageId counter, though they cannot activate these stages. While not a security vulnerability, it represents poor access control design and could lead to contract state pollution with unused stages. Add onlyOwner modifier to maintain consistent access control patterns across all stage management functions.
informational Issues | 2 findings
Resolved
#1 informational Issue
Floating Pragma Version Usage
The contract uses floating pragma ^0.8.25 which allows compilation with any 0.8.x version above 0.8.25. This could lead to unexpected behavior or vulnerabilities if compiled with newer compiler versions that introduce breaking changes or have undiscovered bugs in future releases. Use fixed pragma version: pragma solidity 0.8.25; to ensure consistent compilation behavior across all deployments.
Resolved
#2 informational Issue
Unused code.
Functions that are not used (dead-code).