The domain puffler.finance, impersonating the brand puffer, is currently down after being used for a confirmed phishing operation. This site presented itself as a legitimate financial service, likely to defraud users.
Thirteen out of 95 security vendors, including BitDefender, Fortinet, Kaspersky, and Sophos, flagged puffler.finance as malicious on VirusTotal. The domain appeared on 5 public blocklists, though Google Safe Browsing did not flag it.
GNAME.COM PTE. LTD. registered the domain on 2025-12-28. It was first seen on 2026-02-26, resolving to the IP address 178.16.
Extracted from stored page analysis
Observed indicators
0 wallet · 2 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Telegram
https://t.me/puffer_asiaStored page reference
Telegram
https://t.me/puffer_fiStored page reference
IoC extraction recorded 2026-08-01 04:29:39 UTC
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='puffler.finance', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
DOM Analysisanalyzed 2026年3月24日score 80/1001 brand signal
IoC Extractionscanned 2026年8月1日0 wallet · 2 Telegram IoCs
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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:09:53 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-05-15 22:09:47 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-15 22:09:47 UTC → 2026-09-30 16:14:55 UTC · 3,306.09hmidpoint estimate ≈ 2026-07-23 19:12:21 UTC · precision very low · 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.
技术 · 3 identified
P
Plesk
P
PHP
Programming languages
Server-side scripting language designed for web development.
N
Nginx
Web serversReverse proxies
High-performance HTTP server and reverse proxy, known for stability and low resource usage.
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.
14 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.
(SG)
