Quantstamp reviewed Vector Reserve on 22 Feb 2024: 12 findings, 0 critical; 1 marked fixed, 11 acknowledged.
Report hosted on certificate.quantstamp.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 2 | 1 |
| Low | 0 | 9 | 0 |
A common attack in DeFi is the sandwich attack. Upon observing a trade of asset X for asset Y, an attacker front-runs the victim trade by also buying asset Y, lets the victim execute the trade, and then executes another trade after the victim by trading back the amount gained in the first trade. Intuitively, one uses the knowledge that someone’s going to buy an asset and that this trade will increase its price, to make a profit. The attacker’s plan is to buy this asset cheaply, let the victim buy at an increased price, and then sell the received amount again at a higher price afterward. The swap performed in `swapETHForTokens()` and `addLiquidity()` for LP bonds (`WETHTOLP ` type) currently accept any amount of tokens in return, making them vulnerable to sandwich attacks. The Vector team should be aware of this possible attack, especially if the taxes in the Vector token are disabled, increasing the attacker's profitability, or if the max payout is sufficiently high to cover the fees plus some profit. Additionally, there have been cases with similar token contracts where an attacker could force the token contract to swap its balance in one pool which would lower its price, buy the token low in that pool, and sell it high in the second pool if the token is listed in multiple DEXs.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (30)
236 projects reviewed · 332 reports · latest Oct 2026
See Quantstamp’s auditsSomething 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