Crypto

Mixer, tumbler, and privacy-coin exposure

Crypto deposits that came through a mixer or tumbler, withdrawals sent to one, and customers who move value into privacy coins, found with blockchain analytics.

A deposit that came through a mixer or tumbler, a withdrawal sent to one, or a customer moving value into a privacy coin, found with blockchain analytics Customer Deposit or Withdrawal Mixer or tumbler or Customer Moves value into Privacy coin Found with blockchain analytics

What it catches

Crypto that has been through a service built to hide where it came from. A mixer (or tumbler) takes coins from many users, pools them and pays out the same value from other coins to fresh addresses, so the trail on the blockchain from sender to receiver is broken. FinCEN describes it: mixers “commingl[e] CVC belonging to other mixer users and splitting the value into many small pieces that pass through a number of different intermediary accounts”, so that criminals “trade CVC directly associated with any one particular crime for other CVC of equal value originating from alternative sources”. Privacy coins (anonymity-enhanced cryptocurrencies) do the same by design: their transfers hide the parties or the amounts on their own ledger.

The rule catches three shapes, all listed by regulators:

  • A deposit that came from a mixer, directly or a few transfers back. FATF lists funds deposited or withdrawn from an address “with direct and indirect exposure links to known suspicious sources, including darknet marketplaces, mixing/tumbling services, questionable gambling sites, illegal activities (e.g. ransomware) and/or theft reports”, and “A customer’s funds which are sourced directly from third-party mixing services or wallet tumblers” (FATF, virtual asset red flags, paras 13 and 15).
  • A withdrawal to a mixer: FinCEN’s red flag is simply “A customer initiates a transfer of funds involving a mixing service.”
  • Privacy coins: transactions in them, and trades into them. Nigeria’s virtual asset regulations name “transactions involving … privacy-enhancing coins” among the cases for enhanced due diligence (see By country). FATF lists “Moving a VA that operates on a public, transparent blockchain, such as Bitcoin, to a centralised exchange and then immediately trading it for an AEC or privacy coin” (para 13). FINTRAC lists a “Client portfolio [that] only consists of privacy coins or has a high value in privacy coins” and a client who “transfers Bitcoin in large volumes in exchange for privacy coins”.

FATF’s July 2026 update says VASPs should “Assess risks arising from DeFi activities, including exposure to protocols, bridges, mixers, cross-chain tools, and apply appropriate AML/CFT/CPF measures to mitigate those risks” (Recommendations for the private sector, 6(iv)), and notes that many jurisdictions impose “additional restrictions on higher-risk activities such as anonymity-enhancing services, privacy coins, mining, or custody” (para 15).

You cannot see a mixer by looking at your own ledger: an address is just a string. The rule depends on blockchain analytics, which attribute addresses to services (a mixer, an exchange, a darknet market) and trace how much of the value in a transfer passed through each, and over how many transfers (“hops”). It finds exposure, not crime. FATF says of these anonymity features that “the mere presence of these features in an activity does not automatically suggest an illicit transaction”; people use them for privacy. An analyst decides.

How the rule works

Every crypto deposit and withdrawal is screened with your blockchain analytics provider, withdrawals before they are sent. For each, take the provider’s view of the other side: whether the address belongs to a mixer, tumbler or other anonymity service (direct exposure), and what share of the transfer’s value passed through one within a set number of hops (indirect exposure). Where you list privacy coins, also watch trades into them and transfers of them. Alert on any withdrawal to a mixer, on a deposit straight from one, on a deposit whose indirect exposure is above a set share, on a customer who deposits a transparent coin and trades it into a privacy coin soon after, and on any deposit or withdrawal of a privacy coin.

Direct and indirect exposure are not the same signal. A deposit straight from a mixer’s address means the customer, or whoever paid them, used the mixer; a deposit with a small share of mixed coins five hops back may only mean the coins went through a busy service at some point. That is why indirect exposure needs a share and a hop limit, and direct exposure does not.

Looks at

Every crypto deposit and withdrawal, with withdrawals screened before they are sent. Where you list privacy coins, every trade into one.

Checks

  • The other address: whether your blockchain analytics attribute it to a mixer, tumbler or other anonymity service.
  • Where the value came from: on deposits, the share of the transfer’s value that passed through such a service within the hop limit.
  • The asset: whether it is on your list of privacy coins.

Leaves out

  • Movements between your own wallets (deposit addresses swept to your hot or cold wallets).
  • Incoming transfers below the small-amount floor: they are recorded, not alerted, since anyone can send a tiny amount to any address.

Alerts when

Any of these is true:

  1. A withdrawal goes to an address attributed to a mixer or other anonymity service, whatever the amount.
  2. A deposit comes straight from such an address.
  3. A deposit’s indirect exposure is at least your share of its value.
  4. The customer deposits a transparent coin and trades it into a privacy coin within a short window.
  5. A deposit or withdrawal is in a privacy coin on your list.

How often

One open alert per customer and counterparty address, or per customer for privacy-coin transfers. Later transfers are added to the open alert, so the case shows every one, and each new withdrawal to a mixer comes back to the analyst for review.

Highlighted values are settings you choose. Hover over one, tap it or tab to it for a suggested value.

Common variants:

  • Outgoing block. Screen withdrawals before they are broadcast and hold any that go to a mixer until reviewed. Once sent, a crypto transfer cannot be recalled.
  • Path after a deposit. FINTRAC lists crypto that “passes through mixers/tumblers and is transferred to multiple wallets, where the VC is exchanged for funds”. Combine a mixer-exposed deposit with a quick conversion to fiat or a withdrawal (see Rapid pass-through).
  • Swap hopping. FinCEN lists a customer who “receives CVC from an external wallet, and immediately initiates multiple, rapid trades among multiple CVCs, especially AECs, with no apparent related purpose, followed by a transaction off the platform”. Count trades between assets after a deposit, with extra weight on privacy coins (see Chain-hopping and cross-chain bridge use, which covers the same red flag).
  • Privacy-coin share of the portfolio. For platforms that list privacy coins: alert when they become most of a customer’s holdings or volume, FINTRAC’s first indicator.
  • Retroactive screening. Analytics providers add new attributions every day. Re-screen recent deposits so that an address labelled as a mixer after the deposit still raises an alert.

Data it needs

ShowHide
FieldUsually comes fromIf it’s missing
Customer idaccount or walletRequired.
Direction (deposit or withdrawal)ledgerRequired.
Counterparty wallet addresswithdrawal instruction; deposit transactionRequired. On deposits the sender’s address is often not stored: derive it from the transaction hash. Without it the deposit side of the rule never matches, silently.
Transaction hash and network (chain)blockchain transactionRequired to look the transfer up and to trace it.
Asset and amountledgerRequired. The asset tells privacy coins apart.
Value in one currencyledger, price feedNeeded for the floor and the share.
TimestampledgerRequired.
Analytics result: category of the address (mixer, tumbler, privacy protocol), indirect exposure share, hops, attribution dateblockchain analytics providerRequired for the mixer part of the rule. Store the result with the transfer, so you can show later what the analytics said at the time.
List of your own walletstreasury, custodyNeeded to leave out internal sweeps.
List of privacy coins you supportlisting policyNeeded for the privacy-coin part.

Thresholds

Each row is a setting the rule needs. Each value is a starting point: test it on your own history, then adjust.

ParameterStarting pointWhere it comes from
Direct exposure, withdrawalsany amountA withdrawal to a mixer is the red flag itself (FinCEN).
Direct exposure, depositsany amount above the small-amount floorFATF lists funds “sourced directly from third-party mixing services or wallet tumblers”. The floor keeps out tiny unsolicited transfers.
Indirect exposure share10% of the deposit’s valueA starting value. Lower catches more layered funds and more noise; higher misses mixed coins blended with clean ones. Test it on your own data.
Hop limitset with your analytics providerNo public source gives a number. Exposure many hops back means little on its own.
Small-amount floorset per asset from your own deposit sizesNo public source gives a number.
Privacy-coin window, from deposit to tradeset from your own dataFATF’s red flag is a trade made “then immediately” after the move to the exchange; no public source gives a number.
Privacy-coin deposits and withdrawalsany withdrawal; deposits above the small-amount floorNigeria’s regulations name transactions involving privacy-enhancing coins with no amount (CBN VA Regulations, 26.3.11(f)).

By country

  • Nigeria. The CBN’s Regulations for the Operations of Non-Security Virtual Assets in Nigeria (in force 5 November 2026) bind stablecoin issuers and licensed or authorised virtual asset service providers (VASPs). Enhanced due diligence applies, proportionate to the risks, “where higher AML/CFT/CPF risks are identified, including in relation to” “transactions involving mixers, tumblers, privacy-enhancing coins or other anonymity-enhancing technologies, or high-risk counterparty VASPs” (section 26.3.11(f)); its measures include, “as appropriate”, “analysing the transaction path using blockchain analytics” (section 26.3.12). The licensee must run “an automated transaction monitoring system, supported by blockchain analytics”, configured to alert on transactions consistent with known virtual asset typologies, which the clause says include “mixing or tumbling” (section 26.7.1(c)). Each alert is reviewed and its disposition documented within five business days, or within 24 hours “where the alert indicates a possible sanctions match or terrorist financing” (section 26.7.2). A report to the NFIU includes “wallet addresses, transaction hashes, counterparty VASP details” (section 26.9.3).

    Reporting deadline

    Report to the NFIU “promptly, and in any case within twenty-four (24) hours of forming the suspicion”, regardless of the amount and whether the transaction was “completed, attempted, rejected, suspended or abandoned” (CBN VA Regulations, sections 26.9.1 and 26.9.2). The Money Laundering (Prevention and Prohibition) Act 2022 requires a report “immediately” and a written report within 24 hours after the transaction (s.7(1)–(2)).

  • Rwanda. Law No. 023/2026 regulating virtual asset business (in force on publication, 28 May 2026) defines “mixer or tumbler services” as “a cryptographic facility or service that mixes different streams of potentially traceable virtual assets, thereby concealing the origin of funds of a particular virtual asset” (art. 2(s)). Its definition of a virtual asset leaves out “anonymity-enhanced virtual assets and related activities” (art. 4(3)(h)), which are virtual assets “that incorporate privacy-enhancing features designed to obscure transaction details, participant identities, or asset flow” (art. 2(y)). A legal entity may not operate “a mixer or tumbler service” unless authorised by the Regulatory Authority in collaboration with relevant authorities (art. 15(4)(c)). A natural person who “establishes a mixer or tumbler service or mechanism intended to obscure the ownership of assets without authorisation” commits an offence, punished by a fine of FRW 20,000,000 to 30,000,000, imprisonment of two to three years, or either (set by law, art. 38(1)(d)); where a legal entity commits it, “the penalty imposed is a fine of not less than FRW 70,000,000 but not more than FRW 100,000,000” (art. 38(2)). The article’s heading speaks of the “use of mixer or tumbler services without authorisation” in all three languages; in point (d), the English and Kinyarwanda texts say establishes, the French “met en place ou utilise” (establishes or uses). A VASP “reports all suspicious transactions, including attempted transactions, regardless of the transaction amount” (art. 20(3)).

  • EU. Crypto-asset service providers weigh, as factors that may increase risk, a product that allows transactions with “platforms that aim to obfuscate transactions and facilitate anonymity such as mixer or tumbler platforms” (EBA risk factor guidelines, Guideline 21.3(d)(iv)), a customer who “receives crypto-assets which have been subject to anonymity-enhancing activities” (21.5(b)(xiv)), and one who repeatedly receives from or sends to self-hosted addresses on decentralised platforms “which involve the use of mixers, tumblers and other privacy-enhancing technologies” (21.5(b)(xv)(d)). They “should apply advanced analytics tools” to transactions on a risk-sensitive basis, as a supplement to standard monitoring (21.13). These guidelines apply from 30 December 2024. The EBA’s Travel Rule Guidelines list, among the risk factors that decide which transfers are monitored, “anonymity-enhancing techniques, products or services, including, but not limited to, mixers or tumblers, Internet Protocol (IP) anonymisers and stealth addresses” (EBA/GL/2024/11, para 47(j)(ii)). Since 30 December 2024, the operating rules of a crypto-asset trading platform “shall prevent the admission to trading of crypto-assets that have an inbuilt anonymisation function unless the holders of those crypto-assets and their transaction history can be identified by the crypto-asset service providers operating a trading platform for crypto-assets” (Regulation (EU) 2023/1114 on markets in crypto-assets, art. 76(3); application date, art. 149(2)). From 10 July 2027, the Anti-Money Laundering Regulation prohibits crypto-asset service providers from keeping “any account otherwise allowing for the anonymisation of the customer account holder or the anonymisation or increased obfuscation of transactions, including through anonymity-enhancing coins” (Regulation (EU) 2024/1624, art. 79(1); application date, art. 90), which it defines as crypto-assets “that have built-in features designed to make crypto-asset transfer information anonymous, either systematically or optionally” (art. 2(1), point 25).

  • Canada. FINTRAC’s virtual currency indicators include a client portfolio that “only consists of privacy coins or has a high value in privacy coins”, a client who “transfers Bitcoin in large volumes in exchange for privacy coins”, funds or virtual currency added or withdrawn from an address “with direct and indirect exposure links to known suspicious sources, including darknet marketplaces, mixing/tumbling services”, and virtual currency that “passes through mixers/tumblers and is transferred to multiple wallets, where the VC is exchanged for funds”.

    Reporting deadline

    Submit the report “as soon as practicable after you have completed measures that enable you to establish that there are reasonable grounds to suspect”; “There is no monetary threshold associated with the reporting of a suspicious transaction” (FINTRAC STR guidance, section 4).

  • United States. FinCEN’s guidance splits mixers in two: a person who accepts crypto and retransmits it so that it cannot be traced back to its source is an anonymizing services provider, and “An anonymizing services provider is a money transmitter under FinCEN regulations”; a supplier of software for the same purpose is not, “An anonymizing software provider is not a money transmitter” (FIN-2019-G001, sections 4.5.1(a) and (b)). Its ransomware advisory lists as red flags “A customer initiates a transfer of funds involving a mixing service” and rapid trades “among multiple CVCs, especially AECs”, followed by a transaction off the platform, and names Monero as an anonymity-enhanced cryptocurrency “increasingly demanded by ransomware criminals” (FIN-2021-A004). In October 2026 FinCEN withdrew its 2023 proposal to require special reports on international mixing, citing concern that it “could have a chilling effect on legitimate activity”, and said it “will continue to monitor activity involving CVC mixers for indicia of money laundering, terrorist financing, or other illicit finance activity” (91 FR 63513, 6 October 2026): no mixing-specific report applies, and the advisory’s red flags stand. OFAC removed the Tornado Cash mixer and its addresses from the SDN List on 21 March 2025.

    Reporting deadline

    A money services business files a suspicious activity report “no later than 30 calendar days after the date of the initial detection” of the facts (31 CFR 1022.320(b)(3)).

False positives and tuning

ShowHide

Common innocent explanations: a customer who uses a wallet with built-in coin mixing for privacy; coins bought from an exchange or a payment service that had once received mixed coins; a privacy coin held as an investment; a deposit from a service whose address the analytics mislabelled.

Typical causes of misfires:

  • Exposure far back. With a long hop limit, most coins in circulation show some exposure to a mixer or a large service. Cap the hops, use a share rather than any trace, and weigh direct exposure much more than indirect.
  • Dust. Anyone can send a tiny amount from a tainted address to any wallet, and some do it on purpose. The customer did nothing. Record it, don’t alert on it, and make sure the customer’s later transfers are not flagged because they swept the dust along with the rest of their coins.
  • Repeat alerts on the same address. Without deduplication, a counterparty address the customer uses regularly raises a new alert on every transfer, and the queue fills with the same few addresses. Keep one open alert per customer and address and add later transfers to it, so the analyst sees them in one case; bring it back for review when the attribution changes, the amounts grow or a new withdrawal goes to a mixer.
  • Your own wallets. Sweeps from deposit addresses to your hot and cold wallets look like transfers. List your own wallets and leave them out.
  • Attribution that changes. An address clean on the day of the deposit may be labelled a mixer later, and labels are sometimes withdrawn. Store the analytics result with the transfer, re-screen recent deposits, and record why an alert was closed.
  • A missing sender address. If deposits are stored without the sender’s address, the deposit side of the rule returns nothing and nobody notices. Check how many deposits carry it, and derive it from the transaction hash where they don’t.
  • Sanctioned mixers. A mixer that is itself on a sanctions list is a sanctions match, with its own process and, in Nigeria, a 24-hour review. Send those to sanctions screening rather than treating them as exposure. The reverse also happens: a mixer removed from a sanctions list is still a mixer, so treat it as exposure, not as a sanctions match, and check that your analytics labels and lists have caught up with the removal.
  • Coins whose privacy is optional. Some privacy coins let the sender choose between a transparent and a shielded transfer. The EU’s definition of such coins covers features that work “either systematically or optionally” (AMLR, art. 2(1) point 25). The asset alone does not tell the two kinds of transfer apart: ask your analytics whether a transfer used the privacy feature, and weigh shielded transfers more.
  • Privacy coins as a listed product. Where you list privacy coins, every transfer of one alerts. Keep one open alert per customer, review the customer once with enhanced due diligence, and add later transfers to that case rather than alerting on each.

How to tune: separate direct from indirect exposure; set the hop limit and share with your analytics provider and test them on a month of your own deposits; put a floor on incoming amounts; deduplicate by address; screen withdrawals before they leave; and re-screen recent deposits.

When it fires

ShowHide

Analyst checklist:

  1. Read the analytics detail: direct or indirect exposure, the share, the number of hops, which service, and when the mixing happened compared with the deposit.
  2. Check whether the mixer or the counterparty is on a sanctions list. If it is, follow the sanctions process.
  3. Look at what the customer did next: a quick conversion to fiat, a withdrawal to new addresses, trades between assets, or a move into privacy coins.
  4. Look at the customer’s history: other exposures, a new account, activity out of line with the declared profile.
  5. Trace the path with your analytics. Unless you already suspect the customer, ask where the funds came from, or, for a withdrawal, why the funds are going to a mixer. Once you suspect, do not alert the customer: in Nigeria, where carrying out due diligence would tip the customer off, the VASP does not pursue it and files a suspicious transaction report instead (CBN VA Regulations, 26.3.15), and it may not disclose that a report is being filed or that “an analysis or investigation is being carried out” (26.10.2).
  6. Decide: close with written reasons, apply enhanced due diligence, restrict the account, or report.

An alert is a reason to review, not a suspicion in itself: FATF notes that the presence of anonymity features “does not automatically suggest an illicit transaction” and should be considered “in the context of other characteristics about the customer and relationship, or a logical business explanation”. Each country’s reporting deadline is under By country.

Sources

16 sourcesHide
  1. Central Bank of Nigeria, Payments System Policy Department, Regulations for the Operations of Non-Security Virtual Assets in Nigeria, November 2026, issued by circular PSP/DIR/PUB/CIR/001/004 of 5 November 2026, in force that day; sections 26.3.11(f), 26.3.12, 26.3.15, 26.7.1(c), 26.7.2, 26.9.1–26.9.3, 26.10.2. https://www.cbn.gov.ng/Out/2026/CCD/REGULATIONS%20FOR%20THE%20OPERATIONS%20OF%20NON-SECURITY%20VIRTUAL%20ASSETS%20IN%20NIGERIA.pdf
  2. Money Laundering (Prevention and Prohibition) Act 2022 (Nigeria), s.7(1)–(2). https://www.nfiu.gov.ng/LawsAndRegulations
  3. Republic of Rwanda, Law No. 023/2026 of 25/05/2026 regulating virtual asset business, Official Gazette No. Special of 28/05/2026; arts. 2(s), 2(y), 4(3)(h), 15(4)(c), 20(3), 38(1)(d) and 38(2). https://www.cma.rw/fileadmin/user_upload/law_regulating_virtual_asset_business.pdf
  4. FATF, “Virtual Assets: Red Flag Indicators of Money Laundering and Terrorist Financing”, September 2020: para 13, “Red Flag Indicators Related to Anonymity”, pp.9–10; para 15, “Red Flag Indicators in the Source of Funds or Wealth”, p.15. https://www.fatf-gafi.org/content/dam/fatf-gafi/reports/Virtual-Assets-Red-Flag-Indicators.pdf
  5. EBA, Final Report: Guidelines amending Guidelines EBA/GL/2021/02 on customer due diligence and the factors credit and financial institutions should consider when assessing the money laundering and terrorist financing risk (EBA/GL/2024/01), 16 January 2024, Guideline 21, paras 21.3(d)(iv), 21.5(b)(xiv), 21.5(b)(xv)(d) and 21.13; applies from 30 December 2024. https://www.eba.europa.eu/sites/default/files/2024-01/a3e89f4f-fbf3-4bd6-9e07-35f3243555b3/Final%20Amending%20%20Guidelines%20on%20MLTF%20Risk%20Factors.pdf
  6. EBA, Guidelines on information requirements in relation to transfers of funds and certain crypto-assets transfers under Regulation (EU) 2023/1113 (“Travel Rule Guidelines”, EBA/GL/2024/11), 4 July 2024, section 4.5.3, para 47(j)(ii); applies from 30 December 2024. https://www.eba.europa.eu/sites/default/files/2024-07/6de6e9b9-0ed9-49cd-985d-c0834b5b4356/Travel%20Rule%20Guidelines.pdf
  7. Regulation (EU) 2024/1624 of the European Parliament and of the Council of 31 May 2024 on the prevention of the use of the financial system for the purposes of money laundering or terrorist financing, art. 2(1) point 25, art. 79(1) and art. 90 (applies from 10 July 2027). https://eur-lex.europa.eu/eli/reg/2024/1624/oj
  8. FINTRAC, “Money laundering and terrorist financing indicators—Virtual currency transactions”, published June 2021. https://fintrac-canafe.canada.ca/guidance-directives/transaction-operation/indicators-indicateurs/vc_mltf-eng
  9. FINTRAC, “Reporting suspicious transactions to FINTRAC”, section 4. https://fintrac-canafe.canada.ca/guidance-directives/transaction-operation/str-dod/str-dod-eng
  10. FinCEN, Application of FinCEN’s Regulations to Certain Business Models Involving Convertible Virtual Currencies (FIN-2019-G001), 9 May 2019, sections 4.5.1(a) and (b). https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20Guidance%20CVC%20FINAL%20508.pdf
  11. FinCEN, Advisory on Ransomware and the Use of the Financial System to Facilitate Ransom Payments (FIN-2021-A004), 8 November 2021, pp.5 and 8. https://www.fincen.gov/sites/default/files/advisory/2021-11-08/FinCEN%20Ransomware%20Advisory_FINAL_508_.pdf
  12. 31 CFR 1022.320(b)(3), reports by money services businesses of suspicious transactions. https://www.ecfr.gov/current/title-31/subtitle-B/chapter-X/part-1022/subpart-C/section-1022.320
  13. Regulation (EU) 2023/1114 of the European Parliament and of the Council of 31 May 2023 on markets in crypto-assets (MiCA), art. 76(3) and art. 149(2) (applies from 30 December 2024). https://eur-lex.europa.eu/eli/reg/2023/1114/oj
  14. FATF, Targeted Update on Implementation of the FATF Standards on Virtual Assets and Virtual Asset Service Providers, July 2026, “Recommendations for the Private Sector”, item 6(iv) (p.5), and para 15. https://www.fatf-gafi.org/en/publications/Fatfrecommendations/targeted-updated-virtualassets-vasps-2026.html
  15. FinCEN, “Proposal of Special Measure Regarding Convertible Virtual Currency Mixing, as a Class of Transactions of Primary Money Laundering Concern; Withdrawal”, 91 FR 63513, 6 October 2026. https://www.federalregister.gov/documents/2026/10/06/2026-20429/proposal-of-special-measure-regarding-convertible-virtual-currency-mixing-as-a-class-of-transactions
  16. OFAC, Recent Actions, 21 March 2025, “Tornado Cash Delisting”. https://ofac.treasury.gov/recent-actions/20250321

Ask us

A question about this rule?

A person at Archer reads every question and answers by email.

The Fraud & AML Library is a practical reference, not legal advice. What binds is the regulator’s own text, which every rule and regulation page links.

Get new rules and regulation changes by email

When we add a rule or a regulation changes, we’ll email you.

You can unsubscribe at any time. Privacy policy