Security engines reporting a detection: 11. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Stored evidence for safepal-com.org: VirusTotal recorded 11 detections among 89 scanners on 2026-09-19. 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 safepal-com.org. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 11 detections among 89 scanners in the stored snapshot dated 2026-09-19. 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-09-19 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 safepal-com.org in the snapshot dated 2026-09-20. 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 safepal-com.org 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 safepal-com.org on 2026-09-13. The MetaMask and SEAL blocklist snapshot is dated 2026-09-20 and remains a separate event in the stored timeline. A stored HTTP status 301 was observed for safepal-com.org on 2026-09-20. The HTTP status 301 dated 2026-09-20 records a single response for later comparison. The registration date is separately recorded as 2026-08-21. 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 45.74.7.27 as the observed address in this record. The registration date for safepal-com.org is recorded as 2026-08-21. The SSL issuer is recorded as Let's Encrypt / YR1 in the snapshot dated 2026-09-19. 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 safepal-com.org record states that VirusTotal recorded 11 detections among 89 scanners on 2026-09-19. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-20. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 45.74.7.27. The supported conclusion is bounded to the exact stored observations for safepal-com.org. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to safepal-com.org during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain safepal-com.org 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 safepal-com.org. The stored record does not justify extending that rule to 45.74.7.27 or to other infrastructure records.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
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
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='safepal-com.org', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 10:19:44 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-29 22:14:16 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-29 22:14:16 UTC → 2026-09-30 16:14:55 UTC · 18.01hmidpoint estimate ≈ 2026-09-30 07:14:35 UTC · precision medium · basis bounded
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.
Technologies · 3 identified
U
Ubuntu
Operating systems
Ubuntu is a free and open-source operating system on Linux for the enterprise server, desktop, cloud, and IoT.
Last analyzed First positive detection Previous stored snapshot: 11 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
SOCRadar
Sophos
VIPRE
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.
Threat First Observed2026-09-19 18:21:08 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
safepal-com.org detected and queued for full analysis
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.
Dear Team,
We are writing to report a phishing domain that takes the name of the cryptocurrency wallet SafePal and is indexed under a heading built to be read as that wallet's.
The name safepal-com[.]org is assembled so that it reads as the wallet's genuine address: the word "c
1 report filed for safepal-com.org (1 written by a person) · category: Phishing · source checked
“Dear Team,
We are writing to report a phishing domain that takes the name of the cryptocurrency wallet SafePal and is indexed under a heading built to be read as that wallet's.
The name safepal-com[.]org is assembled so that it reads as the wallet's genuine address: the word "com" is pulled inside the label and ".org" is left on the end. On 11 September 2026 Bing returned the domain under the page title "SafePal | Secure Crypto Wallet & Asset Management", described as "Manage, swap, and secure”
— reported by Anonymous on Sep 12, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
4 evidence signal groups linked0 reports recordedUnverified
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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · safepal-com.org
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.
(NL)
