PhishDestroy has listed musordrop2.win as a suspicious domain. The domain was first observed by PhishDestroy on 2026-10-20. The page title date is not known. Google Safe Browsing did not flag the site on the check date and no external blocklists listed it, while PhishDestroy’s internal list does.
How the scam works
No specific malicious mechanism has been observed for musordrop2.win; the current evidence does not confirm phishing, credential harvesting, malware delivery, or financial fraud. In general, domains flagged as suspicious may be used to lure users into revealing personal data, downloading malicious files, or interacting with fraudulent services. Without concrete behavior, the risk remains uncertain and should be treated cautiously.
Evidence
VirusTotal reported 1 detection out of 92 engines on 2026-10-18, with Gridinsoft flagging the domain. Google Safe Browsing checked on 2026-10-20 returned a clean result. No external blocklists listed the domain as of 2026-10-20, but PhishDestroy’s internal blocklist marked it true. OTX recorded three pulses mentioning musordrop2.win on 2026-10-20.
Infrastructure
The domain was registered on 2026-09-01 through Cloudflare, Inc., 49 days before first observation. The recorded IP address is 188.114.97.3. A TLS certificate issued by Google Trust Services / WE1 was observed on 2026-10-20.
What to do
Visitors should avoid entering any credentials or downloading files from musordrop2.win and monitor accounts for unexpected activity. If credentials were submitted, change passwords immediately. Defenders should add a rule to monitor or block traffic to musordrop2.win and review logs for connections to the recorded IP address.
DOM Analysisanalyzed Oct 20, 2026score 10/1003 brand signals
Submitted URLhttps://musordrop2.win/
Favicon Hash
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Edge-IP reputation is not attributed to this domain.
Nameservers 2
henrik.ns.cloudflare.com
ruth.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WE1
Valid from
2026-09-21 00:44:21
Valid until
2026-12-20 01:44:18
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-20 13:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint9693954a3468531868aa3e3529e7872dbb988c66193806998ea0464f0e68971fCertificate names · 1 SANs
musor30.musordrop2.win
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Open Graph title:MUSOR DROP — кейсы CS2 с RTP 98%. Меньше мусора, больше дропа
Open Graph description:Открывай кейсы CS2 на MUSOR DROP: RTP 98%, апгрейд и контракты, вывод скинов в Steam. Честные шансы на ножи и дорогие дропы — без скрытых комиссий.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · musordrop2.win
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.
4 evidence signal groups linked0 stored notification recordsUnverified
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 musordrop2.win)
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.
(US)
