Neurobro Info
At Neurobro, our vision is to make high-quality crypto insights accessible to everyone - not just professional traders. We believe all users - regardless of background or experience - deserve access to powerful tools and actionable crypto data. By leveraging advanced AI Agents within the Neurobro ecosystem, we simplify complex crypto information and help everyday traders to make smart and informed decisions.
Team and KYC Verification
The team has securely submitted their personal information to SolidProof.io for verification.
In the event of any fraudulent activities, this information will be promptly reported to the relevant authorities to ensure accountability and compliance.
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.
TrustNet DataPulse
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 owner cannot set high fees
The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.
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
Contract can be manipulated by owner functions.
Contract is upgradeable
The contract uses a proxy pattern or similar mechanism, enabling future upgrades. This can introduce risks if the upgrade mechanism is not securely managed.
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 or factory contract can add/remove the liquidity pools.
- The owner or factory contract can add/remove the callers from the contract.
- The owner or factory contract can update the project tax recipient.
- The owner or factory contract can update the swap threshold value.
- The owner or factory contract can update the buy and sell tax to any arbitrary value.
- The owner or factory contract can withdraw ETH and stuck tokens from the contract.
Note - This Audit report consists of a security analysis of the Neurobro 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 Neurobro 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
Findings and Audit result
low Issues | 4 findings
Acknowledged
#1 low Issue
Floating pragma solidity version
Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.
Acknowledged
#2 low Issue
The owner can set fees more than 25%.
The setProjectTaxRates function allows the owner to set buy and sell tax rates to arbitrary values without restrictions, potentially leading to excessive fees (e.g., 100%) or zero fees, disrupting operations and eroding user trust. This lack of validation poses risks like exploitation and operational inefficiency. To address this, enforce reasonable limits (e.g., max 500 basis points), introduce governance or multi-signature approval for rate changes, and implement a cooldown period between updates to prevent frequent or abusive changes. These measures ensure fairness, maintain platform stability, and build user confidence while safeguarding against misuse.
Acknowledged
#3 low Issue
Regain ownership.
The owner can regain ownership after transferring it with the following steps: 1. Call lock function to set _previousOwner to the own address 2. Call unlock function to get ownership back 3. Transfer/renounce ownership 4. Call unlock function to get ownership back Make sure to set the _previousOwnership back to address zero after using the unlock function.
Acknowledged
#4 low Issue
Missing 'require' check. (Potential honeypot)
The owner can set any arbitrary address to the project tax recipient address, including zero address as this can lead to a potential honeypot if the owner has set the address to a contract address that cannot receive ETH. It is recommended that the address cannot be set to a contract address that cannot receive ETH to avoid these circumstances.
optimization Issues | 1 findings
Acknowledged
#1 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.