Coinmerge has 1 public audit report from Cyberscope; dated 24 Jan 2024; no critical findings reported. It also holds 1 deployed contract on 1 chain.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
5 findings are still open or acknowledged in the firms’ reports: 5 low (all open).
Self Cross-Site Scripting (XSS)
CoinMerge - Pentest · CertiK · 24 Jan 2024 · Report ↗
User Enumeration in Login and Sign Up
CoinMerge - Pentest · CertiK · 24 Jan 2024 · Report ↗
L02 - State Variables could be Declared Constant
coinmerge · Cyberscope · 31 Jan 2023 · Report ↗
L04 - Conformance to Solidity Naming Conventions
coinmerge · Cyberscope · 31 Jan 2023 · Report ↗
L16 - Validate Variable Setters
coinmerge · Cyberscope · 31 Jan 2023 · Report ↗
Newest first
1 other security report listed, not counted
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| CoinMerge - Pentest Penetration test of off-chain systemsNot counted as an audit report | Security firm: CertiK | Date: | Scope: —Not recorded; see the report | None open | Findings: 2 medium · 7 low 7 fixed · 2 open | skynet.certik.com ↗ |
| coinmerge | Security firm: Cyberscope | Date: | Scope: 1 address on Ethereum | None open | Findings: 3 low 3 open | IPFS ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 2 |
| Low | 5 | 0 | 5 |
In the `Live Data` form, the backend does not properly sanitize the user input before reflecting it back to the user. The Javascript code is executed in `Usage` and `Live Data` sections.
Open the reportThe `Login` and `Create One` functionalities allow an attacker to infer if an email is registered on the platform based on the server response. When an invalid email is sent to the server, it responds with `something went wrong serving the request: Error: could not authorize user` (Login). Additionally, in the `Create One` feature when a registered email is sent to the server, the response contains the error `something went wrong serving the request: Error: [createAccount] an error occurred: Error: an account with this email already exists`. In both cases, the status code field in the response is `500` and the HTTP error code is also `500`.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the report| Address | Chain | Source code |
|---|---|---|
| 0x8786…2a8e0x87869a9789291a6cec99f3c3ef2ff71fceb12a8e | Chain: Ethereum | Source code: Verified source |
Trustblock holds 1 public audit report for Coinmerge, dated 24 Jan 2024. The latest is by CertiK (“CoinMerge - Pentest”).
Cyberscope wrote the report Trustblock holds for Coinmerge.
5 findings are still open or acknowledged in the firms’ reports: 5 low (all open). No critical finding is reported. Statuses are the security firms’ own.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="coinmerge"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us