About rexscammers.com
rexscammers.com is a non-monetised, public-interest awareness publisher. The site exists so that the next person who searches for the "REX · Virtual Visa Card" — and adjacent crypto / Telegram scams — finds primary-source evidence and a concrete reporting path, rather than only the operators' own marketing pages.
One family's experience, made useful for the next
The site started after a close family member was persuaded to deposit 1,000 USDT (TRC-20) into the REX · Virtual Visa Card Telegram mini app on the promise of an anonymous Visa card with instant withdrawals. Once the deposit landed, the in-app withdrawal silently failed. The operator pivoted through a sequence of escalating requests: share your wallet passphrase, scan this QR code, deposit an extra 30 TRX to "activate" the address, deposit a further 9,000 USDT to reach "Private Access" for "real-time withdrawals". No proof of any successful customer withdrawal was ever produced.
The financial and emotional impact on the family was significant. The next-best use of that experience is this site: the homepage documents the exchange in full, the six-phase tutorial generalises the reporting steps for any crypto or Telegram scam, and the sub-pages on @Rexchangebot, @Rexchanges / Stanislav Reuev, rexcardly.com, rexcompanybusiness.com, and rexcompanybusiness.online catalogue the operator's infrastructure piece by piece.
Primary sources, named operators, redacted victims
- Primary sources only. Telegram chat exports, in-app screenshots, on-chain transaction hashes, archived snapshots, regulator-published filings. Hearsay is not published.
- Verbatim, not paraphrased. Chat content is reproduced word-for-word with only personally-identifying victim data redacted. The operator's public Telegram identity is preserved because the site exists to warn other customers.
- Opinion is labelled. Where the site characterises a pattern (e.g. "wallet drainer", "advance-fee escalation"), the underlying evidence is shown so readers can disagree.
- Standing Right of Reply. Any operator can write to beware@rexscammers.com with verifiable evidence. Corrections are reviewed and published within 7 days.
- Updated provenance. Every page carries a visible "Updated on" date.
No money changes hands
- No advertising on any page.
- No affiliate links anywhere on the site. External links go directly to the named third party (regulator, scam database, wallet vendor, news outlet) without referral tags.
- No donations accepted. The site has no donation page, no crypto address for tips, no Patreon, no Ko-fi.
- No sponsorship. No content on the site has been paid for by any party.
- No paid-removal policy. Operators cannot pay to have the page modified or taken down. Verifiable evidence, submitted via the Right of Reply, is the only mechanism that changes the page.
- No recovery referrals. Victims will not be referred to "recovery agents" or "asset-tracing firms"; pages that solicit those referrals are themselves a documented second-scam pattern.
Transparency, defaults, infrastructure
- The site is a static, plain HTML / CSS / JavaScript build with no framework, no build step, and no third-party trackers. Source-of-truth files live in a Git repository.
- Analytics are cookieless and aggregate-only; no individual visitor profiling.
- The site is served over HTTPS with HSTS and a Let's Encrypt certificate; SSH is hardened to key-only access.
- Evidence images are redacted of all personally-identifying victim data before publication. The original, unredacted images never leave a private device.
One inbox for everything
- Victim submissions: beware@rexscammers.com. Anonymity respected on request. Use the submission template.
- Right of Reply / corrections: same address. See the Right of Reply page for the editorial workflow.
- Press & researcher requests: same address. The unredacted Telegram chat export is available to journalists, law-enforcement officers, and qualified researchers on request.
- Investigator access: the full TRC-20 deposit address (only the prefix and suffix are shown publicly), block-explorer trails, and case-reference numbers from filed reports are shared privately on request.