Tomatoes Finance Permissions Attack

Notice: This page is a freshly imported case study from the original repository. The original content was in a different format, and may not have relevant information for all sections. Please help restructure the content by moving information from the 'About' section to other sections, and add any missing information or sources you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.

Tomatos Finance

The "Tomatos" Finance project gained publicity by airdropping tokens into random wallets. When the victim reached the website, they would receive a standard permissions dialog to interact with the smart contract. If they granted permissions, all their funds would be drained.

This is a global/international case not involving a specific country.

About Tomatos Finance

"Tomatos Finance claims to be an experiment in using farming to bring stablecoins and potential token closer to farmers."

"Hacker triggered simple permission granting and withdrew tokens."

"A user was stolen 10,000 DAI due to Tomatoes.finance. It is understood that the main method of the scam is to induce users to approve permission by airdrop."

"[M]any others fell victim to these rug pulls or similar scams in other projects like Tomatoes.finance."

"The newsletter indicates that a hacker would have triggered a simple authorization and removed tokens. News.bitcoin.com observed that since September 23, there has been no activity on its Medium page."

"Users who receive tokens from the DeFi project tomatoes.finance during the airdrop may face the threat of asset loss. The Telegram channel DeFi Leaks issued a warning."

"Warning from DeFi Leaks: If you receive the token in your wallet, please do not visit its website and finally approve any contract. It seems that through the approval of the website, their contract permissions can steal your tokens."

"The developers of the Tomatos.finance project are expected to make a lot of hype in the DeFi field. They encourage users to participate in profitable agriculture by providing liquidity."

"When they visit the site, the potential victim can grant permission to trigger the withdrawal of the token to the third-party address."

"At the time of writing, the site and the tomatoes.finance medium account are not yet available."

This is a global/international case not involving a specific country.

The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.

Include:

Known history of when and how the service was started.
What problems does the company or service claim to solve?
What marketing materials were used by the firm or business?
Audits performed, and excerpts that may have been included.
Business registration documents shown (fake or legitimate).
How were people recruited to participate?
Public warnings and announcements prior to the event.

Don't Include:

Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
Anything that wasn't reasonably knowable at the time of the event.

There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.

The Reality

This sections is included if a case involved deception or information that was unknown at the time. Examples include:

When the service was actually started (if different than the "official story").
Who actually ran a service and their own personal history.
How the service was structured behind the scenes. (For example, there was no "trading bot".)
Details of what audits reported and how vulnerabilities were missed during auditing.

What Happened

The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.

Key Event Timeline - Tomatoes Finance Permissions Attack
Date	Event	Description
September 24th, 2020 12:00:00 AM	First Event	This is an expanded description of what happened and the impact. If multiple lines are necessary, add them here.

Total Amount Lost

The total amount lost is unknown.

How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?

Immediate Reactions

How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?

Ultimate Outcome

What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?

Total Amount Recovered

It is unknown how much was recovered.

What funds were recovered? What funds were reimbursed for those affected users?

Ongoing Developments

What parts of this case are still remaining to be concluded?

Prevention Policies

The general open and permissionless nature of the blockchain trains many people to not to check the legitimacy of any website or application. Many users join with no education, and have no assistance available when they fall victim to any exploit.