
Redacted domain dossier, minus the house style
We are far too editorially nervous to tell you whether the upstream publisher is correct. We can, however, preserve the dossier, keep the indicators readable, and route every external exit through the source gate.
THE ENABLERS REGISTRY identifies active credential possibly phishing infrastructure hosted at [REDACTED], a domain impersonating Microsoft’s 365 login portal to harvest enterprise user credentials. This malicious activity poses a direct threat to organizations relying on Microsoft cloud services, as it exploits trust in the Microsoft brand to deceive victims into surrendering login credentials. The domain leverages GitHub Pages as a hosting platform, capitalizing on the platform’s reputation to bypass traditional security filters. Given the absence of detections by 95 security vendors on VirusTotal, this threat remains under the radar despite its potential impact.
This domain was flagged using seed 155e06 and exhibits several indicators of compromise. Registered through [REDACTED], the domain resolves to IP address 185.199.108.153 and utilizes a Let’s Encrypt SSL certificate to enhance its appearance of legitimacy. The domain currently shows zero detections on VirusTotal (0/95), indicating it has not yet been widely recognized as malicious by security vendors. While the exact registration date is not publicly available, the domain’s use of GitHub Pages suggests a recent deployment to maximize the window of opportunity before discovery. There are no current entries in major blocklists or reputable threat intelligence feeds, further underscoring its stealthy posture. The combination of GitHub hosting, unflagged status, and SSL encryption creates a convincing facade that could easily deceive end users.
Organizations should immediately block inbound and outbound traffic to [REDACTED] at the network perimeter to prevent access to the credential harvesting page. Users must be advised to scrutinize any unexpected login prompts, particularly those delivered via email or embedded links, and to verify the domain in the URL bar before entering credentials. Since the domain leverages HTTPS, traditional SSL inspection or certificate pinning policies may be required to decrypt and inspect traffic for malicious payloads. Implementing browser-based controls to block access to GitHub Pages domains or enforcing a deny list for known impersonation patterns could reduce exposure. Additionally, enabling multi-factor authentication (MFA) for Microsoft 365 accounts can mitigate the impact of credential theft, as compromised credentials alone would not grant access without secondary verification.
Network Security Intelligence
Threat Response Pipeline
Public Blocklist Status
Evidence Capture
Domain Intelligence
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of [REDACTED] · checked Apr 9, 2026
Evidence & External Reports
Were You Affected by This Site?
If you have interacted with this domain, entered personal information, or connected a cryptocurrency wallet — take immediate action. Below are resources to help you report the incident and protect yourself.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or generate an AI-powered complaint →
Related Domain Reports
Other Domains on 185.199.108.153 6 possibly phishing domains
This IP hosts multiple possibly phishing domains — infrastructure shared across campaigns
[REDACTED] 6 flagged
Other Microsoft Impersonation Domains
These domains also target Microsoft users. View all Microsoft threats →
About This Report: [REDACTED]
This domain security report for [REDACTED] is maintained by THE ENABLERS REGISTRY's automated threat intelligence pipeline. Our system continuously monitors this domain across 95 security vendors on VirusTotal, 1 public blocklists.
The site displays a page titled “Site not found · GitHub Pages”, which may be designed to impersonate Microsoft.
[REDACTED] has been listed on THE ENABLERS REGISTRY as a suspicious domain. Scanned by 95 security vendors — automated detections may take time to update. THE ENABLERS REGISTRY threat analysts continue to monitor this domain.
If you believe this listing is inaccurate, you can submit an appeal. For more information about our methodology, visit our FAQ page.
Check Any Domain
Instant threat analysis with 50+ security engines, AI classification & forensic evidence
Scan NowReport Possibly phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Real-time monitoring of active possibly phishing campaigns & takedown progress
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive
Recommendations & Advice for Victims
An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with [REDACTED] — act now.
What should I do immediately?
Urgent
- Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
- Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
- 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 possibly phishing site
What information should I collect for my report?
FBI guidelines
According to the FBI, the most important details are transaction data:
- Cryptocurrency addresses — scammer's wallet (e.g.,
0x5856...35985) - Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
- Transaction ID (hash) — the unique blockchain transaction identifier
- 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
[REDACTED]) - 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)
- Europol — European cybercrime reporting (EU)
- Chainabuse — flag scam wallets across exchanges & platforms
- Your crypto exchange — contact NASDAQ:COIN/LEI:5493004F7TI6QBM4WX72/FinCEN MSB #31000023456789 support to freeze scammer's address
- Local police — creates an official record, even if they can't act immediately
The FBI recovered over $1 billion in crypto fraud in 2024 thanks to victim reports. Your report matters.
How do crypto scams typically work?
- Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
- Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
- Pig butchering — trust built over weeks via [REDACTED]/WhatsApp/dating apps, then money stolen
- Recovery scams — victims targeted AGAIN by fake "recovery agents" demanding upfront fees. Always a scam
- Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
- AI-powered scams — deepfakes, automated possibly phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
- Use a hardware wallet ([REDACTED], [REDACTED]). Never store large amounts in browser wallets
- Bookmark official sites — never click links from emails, DMs, or ads
- Read every approval — verify permissions before signing. Reject unlimited approvals
- Verify domains — check on THE ENABLERS REGISTRY before interacting. Check HTTPS, spelling, domain age
- "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
How big is the crypto scam problem?
- $51 billion flowed to illicit crypto wallets in 2024 — CoinLedger
- Pig butchering losses grew 40% year over year, now the fastest-growing fraud type
- Only ~5% of victims report — your report helps shut down criminal networks
- FBI recovered $1B+ in 2024 thanks to victim reports — FBI.gov
Sources: FBI · CoinLedger · WorldMetrics
Archive note
If the page below still says “we” or sounds suspiciously confident, that remains the upstream publisher speaking. TER only preserves the record, strips the house branding, and keeps exits wrapped through the source gate.