TL;DR: Banco Central do Brasil is advancing to contract its onchain monitoring and fraud intelligence program after a proof of value found preparatory fraud-to-crypto laundering signals could be surfaced before confirmed incident windows, including one alert 14 hours before funds moved, according to Hypernative. The governance lesson is that supervisory visibility now has to start before dispersion, not after settlement.
At a glance
What this is: Hypernative says Brazil’s central bank is moving toward continuous onchain monitoring to spot preparatory fraud-to-crypto laundering signals before funds disperse across exchanges.
Why it matters: This matters because financial-fraud monitoring now overlaps with digital-asset flow intelligence, forcing IAM, fraud, and supervisory teams to govern detection and response across both traditional and crypto rails.
Context
Crypto fraud monitoring is shifting from post-incident tracing to pre-incident signal detection. In this case, the governance gap is not whether fraud exists, but whether institutions can see the preparatory movement of value before it fragments across multiple venues and becomes difficult to attribute.
For central banks and regulated financial ecosystems, that creates a control problem across fraud intelligence, transaction monitoring, and supervisory decision-making. The article’s core point is that cryptoasset flows can become an early indicator layer for broader financial crime, and traditional monitoring stacks do not reliably cover that layer today.
Key questions
Q: What breaks when crypto fraud monitoring only looks for confirmed transfers?
A: Teams lose the preparatory window. By the time funds have dispersed across exchanges, the pattern is harder to correlate, attribution becomes slower, and supervisory response turns into forensics instead of prevention. Monitoring has to catch the setup behaviour that precedes movement, not just the final onchain event.
Q: Why does preparatory crypto activity create a different supervision problem?
A: Because the risk is distributed before it becomes visible as a single incident. Cross-exchange movement, velocity changes, and asset conversion can indicate a campaign in progress, which means supervisors need campaign-level intelligence rather than isolated transaction alerts.
Q: How can institutions tell whether onchain fraud intelligence is working?
A: Look for whether alerts arrive early enough to support intervention, whether investigators can explain each alert in business terms, and whether the methodology continues to match current fraud routes. A working programme produces usable early warning, not just more noise.
Q: What should fraud, compliance, and security teams do when crypto becomes part of laundering routes?
A: They should align escalation paths, evidence handling, and ownership across the three functions before incidents occur. Crypto routes collapse the old divide between fraud detection and financial crime investigation, so response needs shared context and a common operating model.
Technical breakdown
How preparatory fraud signals surface in onchain flows
Onchain monitoring looks for patterns that are weak on their own but meaningful in combination, such as BRL and crypto volume anomalies, cross-exchange synchronicity, intraday velocity changes, and behavioural markers that resemble known incident fingerprints. The technical challenge is not merely detecting large transfers. It is correlating movement across venues quickly enough to distinguish preparatory laundering from ordinary market activity. That requires continuously updated baselines, incident-linked feedback loops, and enough context to make alerts explainable to investigators rather than opaque anomaly flags.
Practical implication: build monitoring logic around correlated behavioural indicators, not a single-wallet or single-exchange threshold.
Why supervisor-led crypto intelligence differs from transaction surveillance
A regulator is not only trying to stop one transfer. It is trying to understand whether activity in one market segment indicates an emerging fraud pattern that will spread into the wider financial system. That means the control objective is broader than compliance monitoring. It includes early warning, explanation, and supervisory prioritisation. In practice, this shifts the useful unit of analysis from the transaction to the campaign, with investigator support needed to tie alerts back to known fraud fingerprints and market-specific behaviour.
Practical implication: treat crypto monitoring as supervisory intelligence, not just post-trade surveillance.
What changes when monitoring becomes an operated intelligence programme
The article describes a model where detection, methodology maintenance, and incident feedback are operated over time rather than handed over as a static tool. That matters because fraud patterns evolve, exchange behaviour changes, and tuning must follow the threat. The architecture therefore needs ongoing model refinement, reporting cadence, and escalation structure. Without those elements, a monitoring stack quickly becomes stale and loses value exactly when fraud techniques begin to route more heavily through crypto channels.
Practical implication: budget for operating cadence and tuning ownership, not only for platform deployment.
Threat narrative
Attacker objective: The objective is to convert fraud proceeds into dispersed crypto flows that are harder for supervisors and institutions to detect, attribute, and contain.
- Entry occurs when fraud proceeds begin moving into crypto channels and across exchanges before traditional financial controls can fully observe the pattern.
- Escalation follows as multi-venue movement, BRL and crypto volume anomalies, and intraday velocity patterns obscure the preparatory stage of laundering.
- Impact is reached when the funds disperse across exchanges, reducing traceability and making the fraud harder to contain through standard supervisory response.
Breaches seen in the wild
- Twilio 0ktapus breach 2022: SMS phishing of employees exposed 209 Twilio customers and 1,900 Signal users, part of the 0ktapus campaign against 130+ firms.
Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
Crypto fraud supervision is becoming an identity and access problem as much as a payments problem. Once value moves across exchanges and wallets, the governance question is no longer only where the money went, but which actors, accounts, and controls touched it before dispersion. For IAM and fraud teams, that means monitoring has to follow trust relationships across rails, not just authenticate human users at the edge.
Preparatory signal detection is the new control boundary. The article shows that the meaningful failure is not missing the final transfer, but missing the setup behaviour that precedes it. That changes how risk should be framed: the decisive gap is the absence of an early-warning layer that can convert noisy market activity into explainable supervisory intelligence.
Regulatory intelligence will increasingly depend on operating models, not just tooling. The move from proof of value to a productized monitoring programme signals a market where detection, analyst feedback, and governance cadence are bundled together. Practitioners should expect crypto-fraud oversight to resemble continuous control operations more than periodic review.
Explaining anomalous behaviour will matter as much as flagging it. Central banks and financial institutions cannot act on unexplained alerts at scale. A useful crypto monitoring programme has to preserve evidential traceability from signal to incident, otherwise escalation will stall in review queues and the control will not change outcomes.
Onchain monitoring is becoming part of the broader financial crime stack. The article points to a future in which fraud, AML, and digital-asset intelligence cannot be separated cleanly in governance design. Practitioners should plan for shared escalation paths, shared investigation context, and clearer ownership across fraud, compliance, and security.
From our research library:
- U.S. fraud losses are projected to reach $40 billion by 2027.
What this signals
Preparatory laundering detection will become a standard expectation in financial crime monitoring. As crypto routing becomes a practical path for fraud proceeds, teams will be judged less on how quickly they explain the final transfer and more on whether they can surface the setup behaviour in time to matter. The governance shift is toward continuous intelligence, not periodic investigation.
Identity governance and financial crime operations are converging around shared trust signals. When value moves through accounts, exchanges, and wallets, the relevant control question is who can move assets, under what authority, and with what evidence trail. That is a cross-functional control problem, not a siloed blockchain analytics problem.
For practitioners
- Define the crypto early-warning boundary Specify which preparatory behaviours, not just confirmed transfers, must trigger fraud and supervisory review across exchanges and wallets.
- Correlate market behaviour across venues Track BRL and crypto volume anomalies, cross-exchange synchronicity, and intraday velocity together so alerts reflect campaigns rather than isolated transactions.
- Preserve incident-linked investigation context Attach known fraud fingerprints, timeline notes, and analyst findings to each alert so reviewers can explain why a pattern matters.
- Operationalise analyst tuning and feedback Assign ownership for continuous methodology maintenance, alert refinement, and escalation rules so the detection model stays aligned to current fraud routes.
Key takeaways
- Crypto fraud is increasingly being detected at the preparatory stage, before value fully disperses across exchanges.
- The article’s evidence points to a 14-hour early alert, showing that signal correlation can expose laundering setup patterns before confirmed incident windows.
- Practitioners should treat onchain monitoring as a continuous supervisory capability with analyst feedback, not a static detection tool.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 addresses the attack and risk surface, while NIST CSF 2.0, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP API Security Top 10 | API9 — Improper Inventory Management | The article depends on tracking activity across exchanges and venues, where incomplete asset and route visibility creates blind spots. |
| Recommendation — Inventory every exchange, wallet, and data feed that influences fraud monitoring so alert coverage is complete. | ||
| NIST CSF 2.0 | DE.AE-02 — Anomalies are analyzed to understand potential impact | The programme centres on analysing anomalies across crypto and BRL flows to infer fraud risk early. |
| RS.CO-02 — Incidents are communicated to stakeholders in a timely manner | The article emphasises governance structure and reporting cadence for supervisory intelligence. | |
| Recommendation — Triage anomalous flows for campaign-level impact, not just isolated transaction deviation. Define escalation routes and stakeholder notification rules before alerts need to be actioned. | ||
| NIST SP 800-53 Rev 5 | AU-6 — Audit Record Review, Analysis, and Reporting | The methodology relies on continuous review and analysis of behavioural evidence from onchain and market signals. |
| Recommendation — Review monitoring outputs continuously and retain analyst annotations to support investigative follow-up. | ||
| CIS Controls v8 | CIS-8 — Audit Log Management | Continuous monitoring only works when event evidence is retained and searchable across venues and incidents. |
| Recommendation — Centralise log and alert evidence so investigators can reconstruct the fraud timeline quickly. | ||
Key terms
- On-Chain Monitoring: On-chain monitoring is the process of observing blockchain transactions and related activity for risk, compliance, or operational signals. In regulated environments, it must be linked to internal records and escalation workflows so teams can investigate activity, not just observe it.
- Preparatory Signal: A preparatory signal is an early behavioural indicator that suggests an incident or fraud campaign may be forming before the primary loss event occurs. These signals are often weak individually, but become useful when correlated with timing, velocity, venue movement, or known incident fingerprints.
- Fraud Intelligence Network: A shared data source that aggregates abuse patterns, customer histories, and risk indicators across multiple merchants or participants. It helps compensate when local session data is sparse by adding broader context about repeat abuse and emerging patterns.
- Cross-Exchange Synchronicity: Cross-exchange synchronicity is the alignment of movement or behaviour across multiple trading venues that can indicate coordinated activity rather than ordinary market behaviour. In fraud monitoring, it is useful because coordinated dispersion often precedes more obvious laundering or cash-out activity.
Deepen your knowledge
The NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, workload identity, and secrets management. It helps security and identity practitioners connect governance, access, and lifecycle controls across modern environments.
Published by the NHIMG editorial team on October 16, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org