io-bridge.io is a Signal impersonation page detected by PhishDestroy on 2026-10-19. Risk: critical (98/100). Registrar: Megazone. Status: Last known active. Hosting: Amazon.com, Inc. VirusTotal: 4/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 4. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
io-bridge.io is a domain that PhishDestroy first observed on 2026-10-19. The site is currently unreachable but remains on the PhishDestroy blocklist. The domain mimics a cryptocurrency bridge service, which is a common lure for wallet drainers and phishing kits. The page title and content could not be verified at the time of last check.
How the scam works
Cryptocurrency bridge services allow users to swap tokens across different networks. Scam sites like io-bridge.io exploit this trust by presenting a convincing interface that prompts users to connect their wallets or enter seed phrases. Once connected, the site can drain tokens directly or harvest credentials for later theft. Users risk losing funds and exposing sensitive wallet data if they interact with the page.
Evidence
On 2026-10-19, VirusTotal flagged io-bridge.io with 4 detections out of 92 engines, including Forcepoint ThreatSeeker, Fortinet, Gridinsoft, and Kaspersky. The domain is also listed on the PhishDestroy, MetaMask, and SEAL blocklists. OTX pulses recorded 4 community reports linking the domain to suspicious activity.
Infrastructure
The domain was registered on 2026-10-15 with Megazone Corp., dba HOSTING.KR. It is hosted on a server with IP address 13.226.244.40.
What to do
If you visited io-bridge.io, do not connect your wallet or enter any credentials. Disconnect any connected wallets immediately and revoke any suspicious approvals in your wallet settings. Clear your browser cache and cookies, then scan for malware. Report the domain to your wallet provider and local cybercrime units. For defenders, block the domain and IP at the network level and monitor for related infrastructure.
No. PhishDestroy classifies io-bridge.io as a Signal impersonation page (risk: critical, 98/100); it was first detected on 2026-10-19. VirusTotal: 4/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
Is io-bridge.io safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on io-bridge.io. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used io-bridge.io?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
RegistrationCreated Oct 15, 2026 (7d · Very New!)—Expires Oct 15, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 19, 2026
DOM Analysisanalyzed Oct 19, 2026score 98/1002 brand signals
Submitted URLhttp://io-bridge.io/
Favicon Hash
Observed page title
IO Bridge
Automated brand references
AcrossSignal
TLS Certificate
Issued by Amazon / Amazon RSA 2048 M04· stored validity ends in 190 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
13.226.244.40
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Frankfurt am Main, DE
Server header
AmazonS3
Nameservers 2
lara.ns.cloudflare.com
maciej.ns.cloudflare.com
Mail routing 3 MX records
route3.mx.cloudflare.netpriority 16
route1.mx.cloudflare.netpriority 35
route2.mx.cloudflare.netpriority 70
Location describes the IP network.
TLS certificate
Issuer
Amazon / Amazon RSA 2048 M04
Valid from
2026-10-15 00:00:00
Valid until
2027-04-30 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-19 04:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint2636d99de818ecaea39644c69781ef904b01b2a9b882eb81f6dda9bd30775d48Certificate names · 1 SAN
www.io-bridge.io
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-22 10:29:15 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-22 10:29:15 UTClast content: 2026-10-22 10:29:15 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 5 identified
A
Amazon Web Services
PaaS
Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
Amazon S3 or Amazon Simple Storage Service is a service offered by Amazon Web Services (AWS) that provides object storage through a web service interface.
Amazon CloudFront is a fast content delivery network (CDN) service that securely delivers data, videos, applications, and APIs to customers globally with low latency, high transfer speeds.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · io-bridge.io
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same automated brand label: Signal8
Reports with the same collector label. A shared label does not establish impersonation or common ownership. View matching reports →
4 evidence signal groups linked0 stored notification recordsLast known active
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including io-bridge.io)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(NL)
