38,628 Crypto Orders. 10,139 IPs. What Wagyu’s Alleged Leak Means for Monero Privacy.
Alleged Wagyu.xyz swap service data leak by WhiteArmor exposes off-chain metadata linking 38,628 crypto orders and 10,139 IPs to Monero privacy transactions without breaking Monero's cryptography. WhiteArmor published alleged Wagyu.xyz transaction records on October 27, 2026 containing swap order data that links public-chain deposits to Monero destinations and client IPs. The off-chain metadata enables correlation between transparent blockchain activity and privacy-coin conversions, including high-value clusters labeled with hacker and theft attributions. The Monero protocol remains unbroken; exposure stems from the swap service retaining transaction metadata.
Detection / HunterZ.ai
Immediate Actions
- Search proxy and DNS logs for wagyu[.]xyz connections from July 18 to October 26, 2026
- Review any Monero swap transactions by organizational wallets through wagyu[.]xyz
- Alert security teams to transaction-aware phishing referencing real swap order details
Key Takeaways
- 38,628 crypto orders and 10,139 IP-level entries in leaked orders.csv and users_wagyu.csv
- 4,002 completed orders retain populated userDeletedAt field despite still being in the export
- Six XMR bridge withdrawals totaling $1.03 million labeled Poloniex Hacker
- 25 Tornado.Cash-labeled ETH-to-XMR orders total $3.56 million in recorded swap volume
- Records span July 18 to October 26, 2026; WhiteArmor listed Wagyu[.]xyz October 27 to 28
Attack Chain
- Collection: Swap service database exported containing 38,628 crypto orders with wallet addresses, IPs, session metadata
- Exfiltration: WhiteArmor publishes alleged Wagyu[.]xyz data as orders.csv (32MB) and users_wagyu.csv (1MB) via Telegram
- Exposure: Off-chain metadata links public-chain deposits to Monero destinations across 10,139 client IPs
- Correlation: Transaction labels and shared identifiers enable cross-chain wallet clustering investigations
- Impact: Privacy erosion for swap users; transaction-aware phishing and extortion risks emerge
Affected Systems
- Wagyu.xyz no-KYC cryptocurrency swap service platform
- Monero (XMR) cross-chain swap service users
- Ethereum depositors using Wagyu.xyz swap service
- Bitcoin depositors using Wagyu.xyz swap service
- Polymarket.com trading platform (third-party provider compromise per image)
Detection Engineering Assessment
Hunting Hypotheses
| Hypothesis | Telemetry | Stage | FP Risk |
|---|---|---|---|
| Outbound connections to wagyu.xyz swap service between July 18 and October 26, 2026 indicate potential data exposure (T1213) | Proxy or DNS logs showing wagyu.xyz domain resolution and traffic | Collection | Low — wagyu.xyz is a specific crypto swap service |
| Files matching orders.csv (32MB) or users_wagyu.csv (1MB) indicate possession of leaked Wagyu.xyz data (T1567) | File system monitoring and DLP alerts for files matching leaked names and sizes | Exfiltration | Medium — generic filenames may appear in other contexts |
Required Log Sources
- Proxy logs
- DNS resolution logs
- Web application firewall logs
- Network firewall logs
- Cloud storage access logs
Control Gaps
- DLP controls cannot detect exfiltration of database records via legitimate admin access
- No-KYC services lack user verification, complicating breach notification
- Metadata retention policies may not enforce actual deletion across backups
Recommendations
Infrastructure Hardening
- Minimize retention of IP addresses, session IDs, and destination addresses in swap databases
- Implement data minimization and encryption for off-chain transaction metadata
- Audit what delete means across live systems, logs, and backups for actual retention compliance
User Protection
- Warn users about transaction-aware phishing referencing real past swap order details
- Advise users that VPN or Tor use does not erase data submitted to the swap service
- Instruct users to verify any refund or recovery messages through known authentic channels
MITRE ATT&CK Mapping
- domainwagyu[.]xyzAffected no-KYC crypto swap service in data leak
- filenameorders.csvLeaked Wagyu.xyz transaction database, 32MB, 38,628 rows
- filenameusers_wagyu.csvLeaked Wagyu.xyz IP-level activity summary, 1MB, 10,139 rows