On 2026-10-01, 67sixcebeh.surf returned an HTTP status code 502, a recorded response from that date. The domain also appears in the PhishDestroy internal listing, a publisher-owned catalogue entry. Its first observation was recorded on 2026-08-27.
Recorded Evidence
The domain 67sixcebeh.surf was first observed on 2026-08-27. An HTTP check on 2026-10-01 recorded a 502 status code. VirusTotal reported 20 detections across 89 scanners on 2026-09-13. OTX recorded 7 pulses on 2026-09-13. The registrar is Global Domain Group LLC.
Interpretation
The PhishDestroy internal listing, the HTTP response, the VirusTotal scan, and the OTX pulses are separate records with their own dates and scopes. The 2026-08-27 first observation and the 2026-10-01 HTTP check are distinct dated entries, so they can be compared without treating either as a trend. The 2026-09-13 VirusTotal and OTX records share a calendar date but remain independent measurements.
Recommended Actions
For 67sixcebeh.surf, preserve the PhishDestroy internal listing and the HTTP response record as separate source artifacts. Compare the VirusTotal detection record and the OTX pulse record independently in later reviews. Recheck the domain's HTTP response and catalogue entries at a later date to extend the evidence base.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='67sixcebeh.surf', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
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.
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:14:43 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:17:47 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.
Last analyzed First positive detection Previous stored snapshot: 20 detections
alphaMountain.ai
ArcSight Threat Intelligence
BitDefender
Certego
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
Seclookup
SOCRadar
Sophos
Viettel Threat Intelligence
VIPRE
Webroot
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-13 22:17:53 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-12 23:04:50 UTC
Domain state transitioned from alive to dead.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
已捕获威胁
67sixcebeh.surf 已检测到并排入队，待进行全面分析
2026年8月27日
Spamhaus DBL
Spamhaus DBL recorded DBL_BOTNET
2026年9月13日
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
This report concerns an automated cryptocurrency laundering machine on the Polygon network that is used by the operators of an active macOS malware (stealer) campaign.
CONTEXT The malware campaign delivers a macOS stealer via fake "CipherCheck — I'm not a robot" verification p
1 report filed for 67sixcebeh.surf (1 written by a person) · category: Other Hack · source checked
“This report concerns an automated cryptocurrency laundering machine on the Polygon network that is used by the operators of an active macOS malware (stealer) campaign.
CONTEXT The malware campaign delivers a macOS stealer via fake "CipherCheck — I'm not a robot" verification pages. Victims are tricked into pasting a base64-encoded command into Terminal, which installs a persistent LaunchAgent and pulls a second-stage payload from a Polygon smart contract used as a C2 directory (contract 0xA3a”
— reported by Anonymous on Aug 27, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
(US)
