safecoreswap.com
“Safeswap Interface”
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@name.com.
The latest stored availability evidence still shows the domain reachable; 14 days 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.
safecoreswap.com — Letzter bekanntermaßen aktiv (HTTP 200). Markenidentität: Unknown; Betrugstyp: Crypto Drainer. Zusammenfassung der Beweislage: VirusTotal 5/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); PhishDestroy score 88/100. Registrar: Name.com.
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
Zusammenfassung der Beweislage
PhishDestroy first observed safecoreswap.com on Sep 6, 2026. Stored content metadata identifies Unknown as the apparent target. The captured page title is “Safeswap Interface”. Stored page analysis classifies the content as crypto drainer. Campaign clustering links the hostname to the Unknown kit. Current evidence score: 88/100 (critical).
One source contains a positive finding: VirusTotal. VirusTotal recorded 5 detections among 89 engines: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar on Sep 20, 2026 at 02:10 UTC. Non-positive and contextual checks: AlienVault OTX listed 4 community pulse references (not vendor detections) on Sep 10, 2026 at 22:38 UTC. The separate external-blocklist snapshot contained no matches on Sep 21, 2026 at 06:20 UTC. URLQuery recorded no positive detection on Sep 6, 2026 at 23:30 UTC. Google Safe Browsing returned no flag on Sep 20, 2026 at 22:00 UTC. URLScan completed without a malicious verdict (score 0) on Sep 7, 2026 at 17:08 UTC.
HTTP 200 was recorded on Sep 21, 2026 at 02:03 UTC. Registration records for the domain list Name.com, Inc. as the registrar and Aug 10, 2022 as the creation date. At collection time, the hostname resolved to 139.162.7.121 on AS63949 (Akamai Connected Cloud). The IP and ASN identify shared Akamai edge infrastructure; the origin server is not established by this address. The stored server header is nginx/1.10.3 (Ubuntu). DOM analysis on Sep 7, 2026 at 02:22 UTC returned 88/100. The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and URLQuery. IoC extraction on Sep 7, 2026 at 04:00 UTC retained 1 format-validated wallet address and 0 Telegram indicators. TLS metadata lists Let's Encrypt as the certificate issuer with validity through Aug 30, 2026; checked Sep 7, 2026 at 01:02 UTC.
Stored content provides classification context, but only one source contains a positive finding.
Erkenntnisse zur Netzwerksicherheit
Forensic History & Detection Timeline
-
VirusTotal Detections Update Sep 7, 2026 · 16:04 UTCVirusTotal scanner detections updated from 4 to 5. Added scanner alerts: Gridinsoft.
-
VirusTotal Detections Update Sep 7, 2026 · 11:19 UTCVirusTotal scanner detections updated from 3 to 4. Added scanner alerts: alphaMountain.ai.
-
VirusTotal Detections Update Sep 7, 2026 · 04:34 UTCVirusTotal scanner detections updated from 2 to 3. Added scanner alerts: CRDF.
-
VirusTotal Detections Update Sep 7, 2026 · 03:00 UTCVirusTotal scanner detections updated from 1 to 2. Added scanner alerts: Forcepoint ThreatSeeker.
-
VirusTotal Detections Update Sep 7, 2026 · 02:28 UTCVirusTotal scanner detections updated from 0 to 1. Added scanner alerts: SOCRadar.
-
Threat First Observed Sep 7, 2026 · 01:24 UTCDomain ingestion complete. Initial state is marked as alive pointing to IP
139.162.7.121.
Pipeline zur Reaktion auf Sicherheitsbedrohungen
Status der öffentlichen Sperrliste
Evasion analysis
Cloaking & traffic-distribution check
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
- Stored cloaking flag
- Not yet scanned
- Last cloaking scan
- Server header seen by scanner
nginx/1.10.3 (Ubuntu)
Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.10.3 (Ubuntu)
VirusTotal-Analyse
Nachweise und externe Berichte
PD-20260906-40CA8D Recipient: abuse@name.com Abuse notice text as sent to the provider
Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (US): 18 U.S.C. § 1343 - Wire Fraud 18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA) 15 U.S.C. § 45 - FTC Act (Deceptive Practices) Federal laws prohibit wire fraud, computer fraud, and deceptive business practices. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
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