1. Home
  2. DeFi
  3. Malicious USDG Approvals Drained Revenue Users' Wallets, and the Split Looks Like a Drainer Business Model

Malicious USDG Approvals Drained Revenue Users' Wallets, and the Split Looks Like a Drainer Business Model

AI persona · DeFi · David Chen · All content is researched and edited by AI and verified by Super Intelligence. Drafted October 5, 2026. How it works · Report an error

Revenue, a service that markets itself as a bridge for moving funds from X Money into cryptocurrency without know-your-customer checks, has been linked to malicious USDG approvals that allowed attackers to gain unlimited spending permissions before moving funds from users' wallets in the same transaction.

Blockchain security firm Salus said attackers obtained permit signatures from users and submitted them to secure unlimited permission to spend their USDG. Once the approval was granted, the perpetrators immediately called the transferFrom function to move the tokens. Both steps were completed within a single transaction, leaving users with little time to react once their signatures had been submitted.

Funds taken through the transactions were then divided between two addresses controlled by the attackers, with 20 percent sent to one address and 80 percent to another. Salus compared the distribution pattern with the revenue-sharing structure used by the Inferno drainer-as-a-service operation, and separately said Revenue's promotional methods resembled FomoPeek's model of using crypto influencers to reach potential victims. The firm stressed it had not established that Revenue was using Inferno Drainer itself, and the similarities alone do not confirm shared infrastructure.

Table of Contents

How permit signature attacks work

The thefts center on permit signatures, which allow token holders to approve spending without first submitting a separate approval transaction onchain. Once attackers have the signature, they submit it to authorize unlimited USDG spending and follow the approval with transferFrom, a function that lets an approved spender transfer tokens from another address within the limits of the existing allowance.

The method fits a common form of approval phishing in which attackers never need a wallet's private key or seed phrase. The wallet owner signs an authorization, often presented by a malicious site as a routine wallet interaction, that gives another address permission to move specific assets. An unlimited approval leaves the approved address capable of transferring the affected token up to the holder's entire available balance.

Permit signatures are particularly difficult for users to identify because permission is granted through a signed message rather than a conventional onchain approval transaction. In Revenue's case, Salus said the approval and subsequent transfer were executed together, with the stolen USDG then routed toward the two addresses. The firm has not publicly established a total loss figure for the Revenue-related transactions.

The pattern has recent precedent. A similar approval attack in July saw an Ethereum user lose nearly 1 million USD after signing a malicious transaction that gave perpetrators access to move assets from the wallet without further authorization.

Why the 20-80 split caught investigators' attention

The fund distribution is what links the incident to a broader criminal economy. Drainer-as-a-service operations automatically divide stolen assets between affiliates who run the phishing and the developers who provide the underlying software, which is exactly the kind of automated split the Revenue transactions display.

Salus has documented this economy before. The firm previously investigated a fake Hyperliquid website promoted through Google sponsored advertisements after a user lost roughly 550,000 USDC in August. Investigators linked the infrastructure behind that campaign to the Inferno drainer ecosystem, and Salus said its undercover investigation found a service offering malicious scripts, approval command generation, automated draining, cross-chain withdrawals, token swaps and tools for consolidating stolen assets. One advertised feature was automated revenue sharing, dividing phishing proceeds among participants without manual distribution. Groups connected to that infrastructure have been linked to approximately 52.74 million USD in losses across several incidents.

Inferno has surfaced in other large approval phishing cases. An anonymous investor sued Coinbase in May over assets connected to a 2024 phishing theft in which the plaintiff claimed roughly 55 million USD in DAI was stolen after interacting with a fake login page. The complaint alleged Inferno Drainer was used in the attack, and part of the stolen cryptocurrency was later traced to a Coinbase retail account, according to blockchain security firm Zero Shadow.

A service built on top of X Money

Revenue's own business model is central to the story. The service describes itself as a route for moving funds from X Money into cryptocurrency without KYC checks. Its website tells users to sign in with an X account, create an order and send dollars through X Money to the @RevenuePay account, after which Revenue says it sends cryptocurrency to the user-supplied wallet. Advertised payout options include USDC, USDT, SOL and ETH, with orders ranging from 10 to 20,000 USD, a stated daily limit of 20,000 USD per account, and a fee of 2 percent plus 0.50 USD.

Revenue is not part of X or X Money. Its website states the service is independent and unaffiliated with X Corp. or X Payments. X Money itself began rolling out payment services to Premium and Premium+ users in the United States this year, offering peer-to-peer transfers, deposit accounts and a Visa debit card, with yields of up to 6 percent advertised at launch. X had not announced direct cryptocurrency support when the service rolled out, which is the gap Revenue positioned itself to fill.

Warning signs predated the drainer report

Questions surrounding Revenue surfaced several days before Salus disclosed the alleged malicious approvals. On October 1, the project said control of its social media account had been compromised by someone associated with its moderation operation. Revenue temporarily suspended swaps and warned users about activity taking place under its name. Its Telegram channel initially warned that Revenue had not launched a token and told users to avoid tokens claiming an official connection to the project, but posts subsequently appeared promoting a REV token, creating conflicting messages about whether the asset had any official relationship with Revenue.

Salus also noted that Revenue's promotional approach resembled the methods associated with FomoPeek, where key opinion leaders were used to attract users, though the firm provided no evidence that the two operations were run by the same people. Revenue's website remained accessible after the disclosure and continued advertising X Money to crypto conversions when checked.

The uncomfortable lessons for DeFi users

The incident is a textbook illustration of why approval hygiene matters more than key custody in many modern attacks. Users who never leaked a seed phrase still lost funds because a signed message is itself an authorization. Security teams consistently recommend the same defenses: revoke unused allowances regularly using onchain approval tools, treat any signature request from an unfamiliar site as hostile, and be especially wary of permit-enabled tokens, where the signature may not even appear as a transaction in the wallet's history.

It is also a lesson about counterparty risk in gray-market bridges. A no-KYC conversion service operating on top of a payments product that has no official crypto integration was never a supervised institution. When its community was hit by wallet-draining approvals days after a social media compromise, the users holding signed, unlimited allowances were the ones who paid for it.

USDG itself, the token targeted by the approvals, is a regulated stablecoin issued under New York Department of Financial Services oversight, which offers its holders no protection against a signature they granted themselves. The security of a permit-enabled token is ultimately only as strong as the last request the user signed.

Source: Salus via crypto.news, Oct 5, 2026. This article is for informational purposes only and does not constitute investment advice. Digital assets are volatile and carry the risk of loss.

26 Comments

  1. revokeobv
    permit + transferFrom in the SAME tx. no approval tx in your history, nothing to catch. this is the single scariest attack pattern for normal users right now
    1. sigguard_
      permit is the nasty part, no approval tx ever shows in your history. anyone who signed one of those REV promo messages is probably still sitting on a live allowance
    2. usdg_whale_watcher
      @revokeobv the 20/80 split matching inferno affiliate structure is the detail that convinces me this wasnt some solo dev. thats drainer-as-a-service plumbing
    3. glimmercheck_
      seconding the permit point. anyone who touched that bridge should be checking USDG allowances on chain, not trusting a telegram that already contradicted itself about a REV token
    4. 0xkelvin
      yep, and the signed message never touches the mempool so there is no pending tx to catch. your only defense is never signing it in the first place
    5. permit_pat
      thats the scariest part, no pending tx means no alert can fire. by the time you see the transferFrom you already signed it hours ago
  2. sats informant
    no KYC bridge for X Money straight into crypto was the red flag sitting right there in the marketing. anyone who signed that permit handed over unlimited USDG spend
    1. Noor Haeger
      exactly, the no-KYC pitch was the funnel. X Money users with zero wallet hygiene got sold unlimited approvals by influencers they trusted. Salus hedging on attribution but the plumbing screams affiliate crew
  3. Piotr Wolak
    A no-KYC bridge bolted onto a payments product that has zero official crypto support, promoted by influencers. Every red flag was flying before anyone got drained.
    1. onchain_olja
      the no-KYC pitch was the product and the attack vector at the same time. a bridge that skips identity checks was always going to end in drainer affiliate money
  4. mei_darkforest
    the 20/80 split between two addresses matching Inferno revenue sharing is a pretty specific fingerprint. Salus hedging on shared infra but the pattern says enough
    1. Kwame Asare
      @mei the FomoPeek style influencer push is the part that should get more attention. The drainer tech is nothing without the distribution channel
    2. salus_close
      ^ the FomoPeek comparison matters more than the Inferno one imo. influencers as the distribution layer means the next one looks identical until the allowances get drained
  5. vesta_check
    permits make approvals invisible, thats the part that gets me. if you ever signed one of those REV promo messages go check your allowances today, dont wait for a drain tx to find it
  6. revoke_reminder
    approval + transferFrom in the same tx means you have zero seconds to react. check your allowances on revoke.cash today, not after
    1. perm_haze
      checked mine after reading this, found two stale USDG allowances from months back. revoked both in 30 seconds. everyone who touched that bridge should do the same today
    2. meirin_tx
      permit plus transferFrom in a single transaction is the scary part. no pending approval to catch, funds gone the second the sig is used
    3. Roos D.
      just did the same sweep and found a stale USDG allowance from the REV promo era. revoked in seconds. scary how these sit live for months after the news cycle moves on
    4. Nadia Fenn
      revoked my stale USDG allowance right after reading this thread. everyone who touched that X Money bridge should do a sweep today, takes a minute
  7. sz8n_
    their own telegram warning no REV token exists, then REV promo posts appear days later. compromised account or inside job, either way nobody should touch it
    1. Marta Dluska
      compromised account fits the timeline better imo. official no-token warning, then promo posts days later reads like someone got phished and the keys went straight to the affiliate crew
  8. Fiona Oyelaran
    any service pitching X Money to crypto with no KYC was always going to end in a writeup like this. the convenience was the trap
  9. duckworth_ttl
    20 to one address and 80 to another is such a lazy tell. nobody splits a drain two ways unless the affiliate cut was pre-agreed. Salus comparing it straight to Inferno revenue sharing says the quiet part
    1. Ando Merten
      the 20/80 split also lines up with how Inferno pays its affiliates per the Salus writeup. same payout fingerprint across crews usually means the same drainer kit underneath
  10. nullset_
    the 20/80 split is textbook affiliate accounting. salus stopped short of naming inferno outright but nobody splits a drain two ways for fun
  11. allowance_sweep
    the single tx detail deserves more attention. permit and transferFrom in one bundle means the drainer skips the usual approval lag entirely, wallet warnings never get a chance