Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is westabuse@gmail.com.
The latest stored availability evidence still shows the domain reachable; 28 hours has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
winstep[.]cc
“winstep nexus官网下载_Windows桌面Dock美化_winstep nexus mods中文安装包下载”
winstep.cc — Nicht bestätigt. Markenidentität: MetaMask; Betrugstyp: Impersonation. Zusammenfassung der Beweislage: VirusTotal 2/91 (alphaMountain.ai, Forcepoint ThreatSeeker); URLQuery 1 alert; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 88/100. Registrar: Chengdu west dimension….
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
Assessment
Stored evidence for winstep.cc: VirusTotal recorded 2 detections among 91 scanners on 2026-08-13. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for winstep.cc. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 2 detections among 91 scanners in the stored snapshot dated 2026-08-13. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-08-13 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for winstep.cc in the snapshot dated 2026-08-12. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains winstep.cc as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed winstep.cc on 2026-08-12. The MetaMask and SEAL blocklist snapshot is dated 2026-08-12 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-06-11. A URLScan reference was stored on 2026-08-12 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
The source stores 154.221.25.42 as the observed address in this record. The registration date for winstep.cc is recorded as 2026-06-11. The observed server header is recorded as nginx in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The winstep.cc record states that VirusTotal recorded 2 detections among 91 scanners on 2026-08-13. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-08-12. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 154.221.25.42. The supported conclusion is bounded to the exact stored observations for winstep.cc. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to winstep.cc during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain winstep.cc as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to winstep.cc. The stored record does not justify extending that rule to 154.221.25.42 or to other infrastructure records.
Erkenntnisse zur Netzwerksicherheit
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | winstep.cc |
malicious | Sinkholed |
Pipeline zur Reaktion auf Sicherheitsbedrohungen
Status der öffentlichen Sperrliste
Technologien · 3 identified
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
nginx.org 100 % KonfidenzHTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
www.rfc-editor.org 100 % KonfidenzHTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
httpwg.org 100 % KonfidenzVirusTotal-Analyse
Website-Performanceanalyse
Google PageSpeed Insights — mobile performance audit of winstep.cc · checked Aug 12, 2026
Nachweise und externe Berichte
PD-20260812-2069A6 Recipient: westabuse@gmail.com Wurden Sie von dieser Website betroffen?
Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.
Melden Sie sich bei Ihren örtlichen Behörden
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
Jede beliebige Domain prüfen
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenPhishing melden
Melden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenEchtzeit-Bedrohungsfeed
Aktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBleiben Sie auf dem Laufenden, bleiben Sie sicher
Beobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt