DÆTA Info

Decentralized data storage is the next generation of data management—secure, efficient and distributed across multiple nodes. By eliminating central points of failure, it enhances data privacy and resilience, offering a more reliable and scalable solution for modern storage needs. This approach ensures data integrity, reduces risks of hacking and empowers users with greater control over their information.

DÆTA Logo

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.

43.49
PoorExcellent

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

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Select the audit
"\"Manual Review\""
Contract address
0x641c...788a
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Javascript
Onboard date 2024/11/06
Revision date In progress

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 burn function within the contract.

Ownership is not renounced

Contract can be manipulated by owner functions.

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:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. 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.


The audit of your browser extension's codebase identified several critical areas that require immediate attention to enhance security, stability, and performance. High severity issues, such as improper handling of access tokens and the unsafe use of non-null assertions with the useWallet hook, pose significant risks of unauthorized access and runtime errors. Medium severity findings, including hardcoded external URLs, inadequate error handling, and insufficient input validation, further expose the extension to potential vulnerabilities like XSS attacks and inconsistent application states. Additionally, low severity concerns related to duplicated code and clipboard API usage, along with optimization opportunities like preventing unnecessary re-renders and efficient data processing, were noted. Addressing these issues by implementing robust validation, secure storage practices, proper error handling, and performance optimizations will significantly improve the extension's security posture, user experience, and maintainability. It is recommended to prioritize fixing high and medium severity vulnerabilities promptly while also refining code quality and performance to ensure a reliable and secure browser extension.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

high Issues | 5 findings

Pending

#1 high Issue
Handling Access Token
Earnings.tsx
L29
Description

The accessToken retrieved from the external API is stored directly in the React component's state (useState). Storing sensitive tokens in state variables can expose them to potential vulnerabilities, especially if the state is accessed or manipulated by malicious scripts or extensions. This exposure increases the risk of unauthorized access and potential data breaches.

Pending

#2 high Issue
Use of Non-Null Assertion with useWallet()
History.tsx
L6
Description

The component uses a non-null assertion (useWallet()!) when invoking the useWallet hook. This practice assumes that useWallet will always return a non-null value. However, if useWallet does return null or undefined (e.g., if the wallet provider is not available), it can lead to runtime errors, potentially causing the extension to crash or behave unpredictably. Such crashes can expose the extension to denial-of-service (DoS) attacks or other malicious exploits.

Pending

#3 high Issue
Use of Non-Null Assertion with useWallet()
RewardClaim.tsx
L6
Description

The component uses a non-null assertion (useWallet()!) when invoking the useWallet hook. This practice assumes that useWallet will always return a non-null value. However, if useWallet does return null or undefined (e.g., if the wallet provider is not available), it can lead to runtime errors, potentially causing the extension to crash or behave unpredictably. Such crashes can expose the extension to denial-of-service (DoS) attacks or other malicious exploits.

Pending

#4 high Issue
Overwriting window.ethereum May Cause Security Vulnerabilities
WalletProvider.tsx
L7
Description

The line window.ethereum = window.ethereum || {}; overwrites the existing window.ethereum object if it is undefined. This can lead to the application not recognizing legitimate Ethereum providers like MetaMask, potentially causing security issues or malfunctioning wallet interactions.

Pending

#5 high Issue
Use of Non-Null Assertion with useWallet()
Body.tsx
L4
Description

The component uses a non-null assertion (useWallet()!) when invoking the useWallet hook. This practice assumes that useWallet will always return a non-null value. However, if useWallet does return null or undefined (e.g., if the wallet provider is not available), it can lead to runtime errors, potentially causing the extension to crash or behave unpredictably. Such crashes can expose the extension to denial-of-service (DoS) attacks or other malicious exploits.

medium Issues | 11 findings

Pending

#1 medium Issue
Hardcoded External URLs
Earnings.tsx
L28
L40
Description

The component makes axios GET requests to hardcoded external URLs (https://chatgpt.com/api/auth/session and https://chatgpt.com/backend-api/conversations). Embedding external URLs directly within the code can expose the extension to security risks such as man-in-the-middle attacks, data leakage, and unauthorized access. Additionally, if these URLs are compromised, it could lead to severe security breaches within the extension.

Pending

#2 medium Issue
Lack of Error Handling in Axios Requests
Earnings.tsx
L28
L39-35
Description

The axios GET requests for fetching the session and conversations do not include error handling mechanisms. Absence of error handling can lead to unhandled promise rejections, which may crash the application or leave it in an inconsistent state. Additionally, without proper error handling, sensitive information from failed requests might inadvertently be exposed to users or logs.

Pending

#3 medium Issue
Hardcoded External Image URLs
History.tsx
L23,46,61,
Description

The component includes hardcoded external image URLs (e.g., https://svgshare.com/i/1BJw.svg, https://svgshare.com/i/1BKD.svg, https://svgshare.com/i/1BJB.svg, https://svgshare.com/i/1BGS.svg). Relying on external image sources can expose the extension to security risks such as content tampering, man-in-the-middle (MitM) attacks, and availability issues if the external service becomes unreliable or compromised.

Pending

#4 medium Issue
Hardcoded External Image URLs
RewardClaim.tsx
L21
L57
L74
L91
L101
L107
L117
Description

The component includes hardcoded external image URLs (e.g., https://svgshare.com/i/1BJi.svg, https://svgshare.com/i/1BJM.svg, https://svgshare.com/i/1BJh.svg). Relying on external image sources can expose the extension to security risks such as content tampering, man-in-the-middle (MitM) attacks, and availability issues if the external service becomes unreliable or compromised.

Pending

#5 medium Issue
Hardcoded External Image URLs
CSections.tsx
L21
L57
L74
L91
L101
L107
L117
Description

The component includes hardcoded external image URLs (e.g., https://svgshare.com/i/1BHs.svg, https://svgshare.com/i/1BK5.svg). Relying on external image sources can expose the extension to security risks such as content tampering, man-in-the-middle (MitM) attacks, and availability issues if the external service becomes unreliable or compromised.

Pending

#6 medium Issue
Inadequate Error Handling in claimRewards Function
WalletProvider.tsx
L170
Description

The claimRewards function catches errors but proceeds to send messages and alerts even after encountering an error. This can lead to inconsistent application states and poor user experience.

Pending

#7 medium Issue
Lack of Input Validation in verifyRefferalCode Function
WalletProvider.tsx
L186-207
Description

The verifyRefferalCode function does not validate the refCode parameter, potentially allowing malicious or malformed data to be sent to the backend, which can lead to security vulnerabilities such as injection attacks.

Pending

#8 medium Issue
Missing Handling of Ethereum Provider Events Like accountsChanged and chainChanged
WalletProvider.tsx
LNot Implemented
Description

The application does not listen for Ethereum provider events such as accountsChanged or chainChanged. This can lead to the application state becoming out-of-sync with the actual wallet state, causing potential security and usability issues.

Pending

#9 medium Issue
Inadequate Security Checks on Inputs and Messages
WalletProvider.tsx
LVarious
Description

The application does not perform sufficient security checks on data received from user inputs or messages, potentially allowing malicious data to be processed, which can lead to security breaches.

Pending

#10 medium Issue
Missing Input Validation for refCode
Body.tsx
LMultiple
Description

The input value refCode is passed directly to the verifyRefferalCode function without any validation or sanitization. This can lead to security vulnerabilities if malicious inputs are processed.

Pending

#11 medium Issue
Missing Error Handling for verifyRefferalCode
Body.tsx
L63
L71
Description

Calls to verifyRefferalCode do not handle potential errors or exceptions. If the verification fails, this could lead to unexpected behavior or a poor user experience.

low Issues | 11 findings

Pending

#1 low Issue
Missing await for an async function call
background.js
L2
Description

Async function call without an expected await prefix inside an async function. Such call returns a Promise and control flow is continued immediately.

Pending

#2 low Issue
Referenced UMD global variable
CSections.tsx
L9
Description

Usage of a Universal Module Definition (UMD) global variable if the current file is a module (ECMAScript or CommonJS). Referencing UMD variables without explicit imports can lead to a runtime error if the library isn't included implicitly.

Pending

#3 low Issue
Potential XSS via Unsanitized Data
Earnings.tsx
L108
Description

The component passes item.reward directly into the value prop of the ActivityCard component. If item.reward is derived from user-generated content or external sources without proper sanitization, it could be exploited to inject malicious scripts, leading to Cross-Site Scripting (XSS) attacks.

Pending

#4 low Issue
Missing Null Checks and Non-null Assertions
Earnings.tsx
-
Description

The component uses non-null assertions (e.g., useWallet()!) and lacks comprehensive null checks for potentially undefined or null data. This practice can lead to runtime errors if the asserted values are, in fact, null or undefined, causing the extension to crash or behave unpredictably.

Pending

#5 low Issue
Duplicated code fragment
Earnings.tsx
L91-139
Description

Duplicated code fragment

Pending

#6 low Issue
Handling and Displaying User-Generated Content Without Sanitization
History.tsx
L22-27
Description

The component maps over user.histories and directly injects item.reward into the value prop of the ActivityCard component (value={+${item.reward} DaeTa}). If item.reward originates from user-generated content or external sources without proper sanitization, it can be exploited to inject malicious scripts or manipulate the UI, leading to Cross-Site Scripting (XSS) attacks.

Pending

#7 low Issue
Handling and Displaying User-Generated Content Without Sanitization
RewardClaim.tsx
L9-26
Description

The component maps over user.referrals and directly injects item.reward into the JSX ({+${item.reward}}). If item.reward originates from user-generated content or external sources without proper sanitization, it can be exploited to inject malicious scripts or manipulate the UI, leading to Cross-Site Scripting (XSS) attacks.

Pending

#8 low Issue
Clipboard API Usage Without Validation
RewardClaim.tsx
L36-44
Description

The component uses the Clipboard API (navigator.clipboard.writeText) to copy the invite code to the clipboard. While functional, this implementation does not validate the invite code before copying. If user._doc.code is undefined or contains unexpected characters, it can lead to incomplete or incorrect data being copied, potentially confusing the user or leading to unsuccessful referrals.

Pending

#9 low Issue
Unreliable Use of setTimeout for Awaiting Transactions
WalletProvider.tsx
L125
Description

The use of await new Promise((resolve) => setTimeout(resolve, 5000)); is an unreliable method to wait for transaction confirmations, as it assumes a fixed delay which may not align with actual transaction times.

Pending

#10 low Issue
Missing Validation of Network After Switching Chains
WalletProvider.tsx
-
Description

After attempting to switch the Ethereum chain, the code does not verify whether the switch was successful by checking the current network's chainId. This omission may result in the application operating on an unintended network.

Pending

#11 low Issue
Hardcoded Extension ID Exposes Internal Identifiers
Hardcoded Extension ID Exposes Internal Identifiers
L29
Description

The extension ID is hardcoded into the source code (const extensionId = "olicmopfdmbpgacjdndpifmkndpgcmpm";). This practice can expose internal identifiers and may allow for misuse or spoofing if the ID is sensitive.

optimization Issues | 7 findings

Pending

#1 optimization Issue
Pointless statement or boolean expression
Earnings.tsx
L165
Description

Pointless or pointlessly complicated boolean expression or statement.

Pending

#2 optimization Issue
Unnecessary Re-Renders
ActivityCard.tsx
-
Description

The ActivityCard component lacks memoization. In browser extensions, where multiple components might render frequently, unnecessary re-renders can impact performance.

Pending

#3 optimization Issue
Inefficient Data Processing
Earnings.tsx
L36-86
Description

The component employs nested for loops to filter and process conversations, resulting in a time complexity of O(n²). This approach can lead to performance degradation, especially when handling large datasets, as the number of operations increases exponentially with the size of the input.

Pending

#4 optimization Issue
Inefficient Rendering with Index as Key
History.tsx
L11,
Description

The component uses the array index (idx) as the key prop in the map function when rendering history items. Using indices as keys can lead to performance issues and unexpected behavior, especially if the list can change dynamically (e.g., items being added, removed, or reordered). This practice can cause unnecessary re-renders and affect the component's efficiency.

Pending

#5 optimization Issue
Repetitive Date Conversion
History.tsx
L17
Description

The component calls convertTimestamp(new Date(item.created_at).getTime() / 1000) within the map function for each history item. Performing this conversion for every render can lead to unnecessary computational overhead, especially with large datasets, impacting the component's performance.

Pending

#6 optimization Issue
Repetitive Creation of External Image Requests
RewardClaim.tsx
Lmultiple
Description

The component includes multiple external image requests within the JSX. Each image request can lead to additional network overhead, impacting the component's performance, especially if the images are large or the network is slow. Additionally, without proper caching strategies, the same images may be fetched repeatedly, leading to inefficient resource usage

Pending

#7 optimization Issue
Use of Index as Key in Mapping Function
CSections.tsx
L66
Description

The component uses the array index (index) as the key prop in the map function when rendering navigation buttons. Using indices as keys can lead to performance issues and unexpected behavior, especially if the list can change dynamically (e.g., items being added, removed, or reordered). This practice can cause unnecessary re-renders and affect the component's efficiency.

informational Issues | 7 findings

Pending

#1 informational Issue
DOM Clobbering Gadget found in rollup bundled scripts that leads to XSS
package.json
-
Description

rollup <2.79.2 Severity: high node_modules/@crxjs/vite-plugin/node_modules/rollup @crxjs/vite-plugin 2.0.0-beta.1 - 2.0.0-beta.26 Depends on vulnerable versions of rollup node_modules/@crxjs/vite-plugin 2 high severity vulnerabilities

Pending

#2 informational Issue
Result of method call returning a promise is ignored
Earnings.tsx
L32
L88
L169
Description

A function call that returns a Promise that is not used later. Such calls are usually unintended and indicate an error.

Pending

#3 informational Issue
Result of method call returning a promise is ignored
WalletProvider.tsx
L55
L59
L210
Description

A function call that returns a Promise that is not used later. Such calls are usually unintended and indicate an error.

Pending

#4 informational Issue
Result of method call returning a promise is ignored
background.js
L24
Description

A function call that returns a Promise that is not used later. Such calls are usually unintended and indicate an error.

Pending

#5 informational Issue
Presence of Dead Code
ActivityCard.tsx
L13
Description

There is a commented-out alternative logo URL. Dead code can clutter the codebase, making maintenance more challenging.

Pending

#6 informational Issue
Image Load Failure Not Managed
ActivityCard.tsx
L21
Description

No handling is in place for scenarios where the image fails to load, potentially resulting in broken images within the extension's UI.

Pending

#7 informational Issue
Potential Typo in Function Name
Body.tsx
L9
L63
L71
Description

The function verifyRefferalCode likely contains a typo in the word "Referral." This can lead to confusion and reduce code maintainability.