TokenOps security record

Ethereumtokenops.io

As of 25 Oct 2026, TokenOps has 1 audit report on Trustblock, by Quantstamp, dated 20 Sep 2023. That report lists no open critical findings.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.

Audits1

Newest first

AuditSecurity firmDateScopeCritical findingsReport
TokenOpsSecurity firm: QuantstampDate: Scope: Files named in the reportNo open critical findingsOpen · certificate.quantstamp.com

Findings5

Statuses are the security firm’s own, from each report.

SeverityOpenAcknowledgedFixed
Critical000
High001
Medium010
Low012
MediumThe Current Access Control Model Can Result in Concurrent BehaviorsTokenOps · Quantstamp · 20 Sep 2023Acknowledged

The current access control based on having several addresses having the role `admin` can negatively impact the system: 1. If one admin address is compromised, it can become the only admin by removing all other admins; 2. One admin address can front-run actions from another admin. For instance, it can create a grant for an address by allocating tokens deposited to the contract for another grant about to be created. 3. One admin can revoke all active grants via the function `revokeGrant()` and withdraw the unlocked tokens via the function `withdrawAdmin()`. 4. One admin can withdraw the unrelated tokens sent to the contract via the function `withdrawOtherToken()` and keep them for himself. 5. The admin could front-run other admins in case of admin access removed by others. In this case, a malicious admin could not be removed. The root cause of this issue is that each admin can trigger an action, even if it is against the interest of the system and all other admins are against this action.

Open the report
LowFunction `withdrawOtherToken()` Is Vulnerable to Double-Entry TokensTokenOps · Quantstamp · 20 Sep 2023Acknowledged

The function `withdrawOtherToken()` can be used by an address with the role `admin` to withdraw tokens from the contract which have a different address than the vested token having the address `tokenAddress`. However, an ERC20 token can have two addresses. Tokens with this special design are called "double-entry tokens". If such type of tokens would be vested by the current contract, using the secondary address would make it possible to drain allocated tokens from the vesting contract. The severity of this issue is assessed as low, because only the admin of the contract can execute this function and double-entry tokens are an uncommon design.

Open the report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

The repositories and files the reports name

Show this on your site

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.

Content

Facts

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.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="tokenops"
></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