VirusTotal
15 / 92 engine detections
Open reportchainxpakpro.org is a Signal impersonation page detected by PhishDestroy on 2026-10-24. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: Omegatech LTD. PhishDestroy sent 1 abuse report. VirusTotal: 15/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
“Chainxpakpro — AI Platform for Smarter Portfolio Decisions”
15 / 92 engine detections
Open report2 det.
Open reportMalicious
Open reportDBL_SPAM
2 community references
Open reportNo threat flag
Open reportPage capture
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy added chainxpakpro.org to its internal blocklist on 2026-10-24 after the intake reason cited multiple VirusTotal detections. The recorded page title reads “Chainxpakpro — AI Platform for Smarter Portfolio Decisions”. An HTTP request on the same day returned a 200 status code, indicating the site was reachable at that time. No further behavior was observed beyond the listed metadata.
The listing does not confirm a specific fraud technique, but the combination of phishing, malware and DGA tags suggests the domain could be used to lure users into disclosing credentials, downloading malicious code, or participating in automated bot activity. Such schemes typically present a legitimate‑looking service to gain trust before delivering the payload or harvesting data.
VirusTotal scanned the domain on 2026-10-24 (analysis date 2026-10-23) and reported 11 malicious and 4 suspicious detections out of 92 engines, with vendors including BitDefender, G‑Data and Kaspersky flagging it as phishing or malware. Google Safe Browsing checked on 2026-10-24 and did not flag the site. Two urlscan captures were recorded: the 2026-10-13 scan returned a clean verdict, while the 2026-10-24 scan showed engine scores of 99 % malicious but an overall non‑malicious classification. Cloudflare Radar on 2026-10-24 marked the domain as malicious, categorising it under malware and scam. OTX listed two pulses referencing the domain as of 2026-10-24. PhishDestroy’s internal blocklist marks the domain as blocked, while external blocklists returned zero matches on the same date.
The domain was registered with Dynadot Inc on 2026-09-28. The recorded IP was 158.94.210.119, associated with the network Omegatech LTD in the Netherlands. TLS was provided by Let’s Encrypt (valid 2026-10-12 to 2027-01-10) using TLS 1.3 and AES‑128‑GCM. Open ports observed were 22, 80 and 443, and the nameservers were ns1.dyna-ns.net and ns2.dyna-ns.net.
Visitors should avoid entering credentials, personal data or downloading files from this site; if any information was submitted, change related passwords and monitor accounts for suspicious activity. No wallet‑related recommendations apply. Defenders should block chainxpakpro.org at network perimeters, log DNS and HTTP requests to the recorded IP, and share the indicator with threat‑intel platforms. Continuous monitoring is advised as the domain’s status may change.
No. PhishDestroy classifies chainxpakpro.org as a Signal impersonation page (risk: critical, 100/100); it was first detected on 2026-10-24. VirusTotal: 15/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on chainxpakpro.org. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
ns1.dyna-ns.netns2.dyna-ns.netLocation describes the IP network.
5d3f58b4608b000bbe2a96f24309496b9fadedb6ee0c540f4379b4a3e3802590chainxpakpro.orgSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of chainxpakpro.org · checked Oct 24, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://chainxpakpro.org/https://chainxpakpro.org/Cache-Control: no-cache, no-store, must-revalidateContent-Encoding: gzipContent-Type: text/html; charset=utf-8X-Powered-By: Expressh3=":443"; ma=2592000no-cache, no-store, must-revalidategzip432text/html; charset=utf-8Sat, 24 Oct 2026 08:03:52 GMTsame-originAccept-Encoding1.1 CaddynosniffExpressValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a16cef-5ed8-7128-a579-496ad118f18e |
|---|---|
| Final url | https://chainxpakpro.org/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://chainxpakpro.org/",
"from": "http://chainxpakpro.org/",
"status": 307
},
{
"to": "http://chainxpakpro.org/",
"from": "https://chainxpakpro.org/",
"status": 307
},
{
"to": "https://chainxpakpro.org/",
"from": "http://chainxpakpro.org/",
"status": 301
}
] |
| Ip | 158.94.210.119 |
| Contacted IP addresses | [
"158.94.210.119"
] |
| Asns | [
"202412"
] |
| Countries | [
"NL"
] |
| Document hash | 870a563e5809619016fc2b0d17743d12c49aaf7439a67dfc70ab40bdeff83c27 |
| Script hashes | [
"8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce"
] |
| Globals | [
"__dclq",
"__dclOrig",
"__dclFlush",
"__smsCheckBeforeSubmit",
"__isSmsEnabled",
"__isSmsVerified",
"intlTelInput"
] |
| Cookies | [
"connect.sid"
] |
| Tls | {
"san": [
"chainxpakpro.org"
],
"cipher": "AES_128_GCM",
"issuer": "YE2",
"subject": "chainxpakpro.org",
"protocol": "TLS 1.3",
"valid_to": "2027-01-10T11:11:06Z",
"valid_from": "2026-10-12T11:11:07Z"
} |
| Domain age days | 26 |
| Apex age days | 26 |
| Tls age days | 11 |
| Tls valid days | 89 |
| Requests | 10 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 99,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"content-type": "text/html; charset=utf-8",
"x-content-type-options": "nosniff",
"referrer-policy": "same-origin"
} |
Observed: · Retrieved:
| Uuid | dd27d371-5730-4985-b71f-acef51054aa2 |
|---|---|
| Final url | https://chainxpakpro.org/ |
| Status | 200 |
| History | [
{
"url": "https://chainxpakpro.org/",
"status": 200
}
] |
| DOM structure hash | 5db5e4183f8dd0d2be4bc08b6c04eb941a1c6581b4ede1677ea5a8386edaef7a |
| Document hash | aa656ae97c67e0d9269d696bb1c4d4ccf022bbc556a507b67bbfb5fcff282e7c |
| Phishing v2 | [
"phishing"
] |
| Url risks | [
"Scam"
] |
| Domain risks | [
"Scam",
"Security threats",
"Newly Seen Domains",
"Security Risks",
"New Domains",
"Malware",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "chainxpakpro.org",
"type": "A",
"value": "158.94.210.119"
}
] |
| Dnssec valid | false |
| Ip | 158.94.210.119 |
| Verdict | {
"tags": [
"malware"
],
"malicious": true,
"categories": [
"malware"
]
} |
| Registration record | {
"registrar": "Dynadot Inc",
"created": "2026-09-28T06:36:26Z",
"updated": "2026-10-11T16:40:58Z",
"expires": "2027-09-28T06:36:26Z",
"nameservers": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 46,
"malicious": 11,
"suspicious": 4,
"undetected": 31
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"DNS8": "suspicious",
"ESET": "suspicious",
"VIPRE": "phishing",
"G-Data": "phishing",
"Sophos": "malware",
"Fortinet": "spam",
"Netcraft": "malicious",
"SOCRadar": "phishing",
"Kaspersky": "phishing",
"Seclookup": "malicious",
"Gridinsoft": "suspicious",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| Registrar | Dynadot Inc |
| Created | 2026-09-28T06:36:26Z |
| Expires | 2027-09-28T06:36:26Z |
| Updated | 2026-09-28T06:41:21Z |
| First seen | 2026-09-29T02:41:36Z |
| DNS records | [
{
"ttl": 300,
"type": "A",
"value": "158.94.210.119"
},
{
"ttl": 300,
"type": "NS",
"value": "ns1.dyna-ns.net"
},
{
"ttl": 300,
"type": "NS",
"value": "ns2.dyna-ns.net"
},
{
"ttl": 300,
"type": "SOA",
"rname": "hostmaster.chainxpakpro.org",
"value": "ns1.dyna-ns.net"
}
] |
| Dns at | 2026-10-23T15:14:03Z |
| Jarm | 40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319 |
| Certificate | {
"san": [
"chainxpakpro.org"
],
"issuer": "Let's Encrypt / YE2",
"serial": "544e68124499c070fca734063e6d71f5ea8",
"sha256": "5d3f58b4608b000bbe2a96f24309496b9fadedb6ee0c540f4379b4a3e3802590",
"subject": "chainxpakpro.org",
"valid_to": "2027-01-10T11:11:06Z",
"valid_from": "2026-10-12T11:11:07Z"
} |
| Registration record | {
"registrar": "Dynadot Inc",
"registrar_iana_id": "472",
"registrar_url": "http://www.dynadot.com",
"created": "2026-09-28T06:36:26Z",
"updated": "2026-09-28T06:41:21Z",
"expires": "2027-09-28T06:36:26Z",
"status": [
"addPeriod",
"clientTransferProhibited"
],
"nameservers": [
"laylah.ns.cloudflare.com",
"simon.ns.cloudflare.com"
],
"dnssec": "unsigned"
} |
| Registry data | {
"status": [
"transfer prohibited"
],
"events": {
"expiration": "2027-09-28T06:36:26Z",
"last changed": "2026-10-12T04:52:56Z",
"registration": "2026-09-28T06:36:26Z",
"registrar expiration": "2027-09-28T06:36:26Z",
"last update of RDAP database": "2026-10-23T11:17:30Z"
}
} |
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Caa records | {
"domain": "chainxpakpro.org"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_by": [
"CloudFlare Family"
],
"blocked_count": 1
} |
| Web archive observations | {
"last": "2026-10-24T08:04:40Z",
"first": "2026-09-28T08:34:02Z",
"changes": 1,
"days_archived": 2,
"scans_per_day": 0.04,
"avg_page_bytes": 22435
} |
| Crawler rules | {
"agents": [
"*"
],
"present": true,
"sitemaps": [
"https://chainxpakpro.org/sitemap.xml"
]
} |
| Sitemap | {
"present": true,
"url_count": 5
} |
| Page title and metadata | {
"title": "Chainxpakpro — AI Platform for Smarter Portfolio Decisions",
"robots": "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1",
"description": "Chainxpakpro offers real-time AI-driven analysis of market and portfolio data, helping you surface risk and support decisions with a fully auditable, FCA-aligned process. Request a technical briefing today.",
"canonicalUrl": "https://chainxpakpro.org/"
} |
| Trackers | {
"requests": 21,
"trackers": [
{
"name": "Cloudflare",
"company": "Cloudflare",
"country": "US",
"category": "Hosting",
"requests": 1
},
{
"name": "jsDelivr",
"company": "jsDelivr",
"category": "Hosting",
"requests": 3
}
]
} |
| Forms and mixed content | {
"third_party_scripts": 0
} |
| Status | {
"up": true,
"code": 200,
"timings": {
"dns": 317,
"tls": 74,
"wait": 90,
"connect": 65,
"download": 131
},
"response_ms": 677
} |
| TLS connection | {
"alpn": "h2",
"cipher": "TLS_AES_128_GCM_SHA256",
"protocol": "TLSv1.3",
"versions": [
"TLSv1.2",
"TLSv1.3"
],
"authorized": true,
"forward_secrecy": true
} |
| Ports | {
"open": [
22,
80,
443
]
} |
| Carbon | {
"bytes": 76439,
"co2_grams": 0.0028,
"cleaner_than": 28
} |
| Dns server | {
"ns": [
{
"ip": "162.159.24.5",
"host": "ns2.dyna-ns.net"
},
{
"ip": "162.159.27.158",
"host": "ns1.dyna-ns.net"
}
],
"zone": "chainxpakpro.org"
} |
| Cookies | {
"cookies": [
{
"name": "cf-c",
"http_only": true,
"same_site": "Lax"
},
{
"name": "__cf_clicked"
},
{
"name": "ph_phc_t6w4wzJE2sbz4ro8LmZZTssm5go3KD6mP7QsqcDQRSp6_posthog",
"secure": true,
"same_site": "Lax"
}
]
} |
| Location | {
"ip": "158.94.210.119",
"asn": "202412",
"org": "Omegatech LTD",
"city": "Amsterdam",
"country": "NL"
} |
| Ssl | {
"issuer": "Let's Encrypt / YE2",
"subject": "chainxpakpro.org"
} |
| DNS records | {
"A": [
"158.94.210.119"
],
"NS": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
],
"SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.chainxpakpro.org\", \"serial\": 2026101103, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Hsts | {
"message": "Site does not serve any HSTS headers."
} |
| HTTP security policies | {
"xFrameOptions": false,
"referrerPolicy": "same-origin",
"xXSSProtection": false,
"permissionsPolicy": false,
"xContentTypeOptions": "nosniff",
"contentSecurityPolicy": false,
"strictTransportPolicy": false,
"crossOriginOpenerPolicy": false,
"crossOriginEmbedderPolicy": false,
"crossOriginResourcePolicy": false
} |
| Get ip | {
"ip": "158.94.210.119",
"family": 4
} |
| Redirects | {
"chain": [
"https://chainxpakpro.org"
]
} |
| Page links | {
"internal_count": 9
} |
| Registration record | {
"registrar": "Dynadot Inc",
"created": "2026-09-28T06:36:26Z",
"updated": "2026-10-11T16:40:58Z",
"expires": "2027-09-28T06:36:26Z",
"status": [
"clientTransferProhibited https://icann.org/epp"
],
"nameservers": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
]
} |
| HTTP headers | {
"headers": {
"content-type": "text/html; charset=utf-8",
"x-content-type-options": "nosniff",
"referrer-policy": "same-origin"
}
} |
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
Reachable
PD-20261024-AA0BAE
2 community references
View sourceNo threat flag
View source15/92 engine detections
View sourcePage captured
View sourcechainxpakpro.org
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
chainxpakpro.org
PD-20261024-AA0BAE Recipient: abuse@omegatech.sc Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance
Federal tips line1-800-CALL-FBICurrent service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.
Contact centre0300 123 2040Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
chainxpakpro.org)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.