The domain chrome-extension-dfhsdfhjgsjsgjsyuou.airdrop.investments was registered through NameCheap, Inc. on May 11, 2026. Since its creation the domain has appeared on a single external blocklist and is actively blocked by the PhishDestroy service. VirusTotal analysis shows that 17 of 91 scanned security vendors have flagged the domain as malicious, providing a modest level of cross‑vendor corroboration.
The campaign is categorized as a crypto drainer and has been assigned an elevated risk rating while remaining active at the time of reporting. No public IP address, hosting ASN, SSL certificate, HTTP status, or page‑title information has been disclosed, leaving the underlying hosting infrastructure and site content uncharacterised. Likewise, brand, kit, or detailed payload information are not currently available, so the precise method used to compromise cryptocurrency assets cannot be confirmed.
Defenders should incorporate the full domain name into inbound and outbound filtering policies, enforce DNS query logging for the domain, and ensure endpoint protection products are updated to reflect the 17 vendor detections. Ongoing monitoring is advised, as additional indicators such as hosting details or malicious payload samples may surface, and threat‑intel sharing with peer organisations can help accelerate detection of related infrastructure.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='chrome-extension-dfhsdfhjgsjsgjsyuou.airdrop.investments', port=80): Max retries exceeded
For the registrable domain airdrop.investments behind this subdomain, 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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:12:11 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 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.
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-08-05 22:54:31 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-07-29 07:35:57 UTC
Domain ingestion complete. Initial state is marked as unknown.
威胁响应 Pipeline
发现
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
(US)
