VirusTotal
14 / 91
إبلاغEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Claim Your $PENGU | Pudgy Penguins”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse-trusted.savcom@in.wixanswers.com.
The latest stored availability evidence still shows the domain reachable; 3 months 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.
pudgy.social — آخر نشاط معروف (HTTP 301). نوع الاحتيال: Crypto Drainer. ملخص الأدلة: VirusTotal 14/91 (ChainPatrol, alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker); URLQuery 3 alerts; Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. مسجّل النطاق: Sav.com.
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
14 / 91
إبلاغEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
3 threat-system alerts
إبلاغAlerts refer to the preserved scan. They do not describe the current state of the site.
2 external matches
التفاصيلA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
17 community references
إبلاغCommunity publication references, not a vendor verdict or evidence of a common operator.
التقرير المخزن
View stored capture ↗ إبلاغA preserved page image documents what the collector received; a capture is not a safety verdict.
اكتمل التحليل
إبلاغThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
إبلاغA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | pudgy.social |
malicious | Sinkholed |
| DNS4EU | pudgy.social |
malicious | Sinkholed |
| DNS4EU | claim.pudgypenguins.com |
malicious | Sinkholed |
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
The domain pudgy.social is suspected of engaging in crypto drainer phishing activities and is currently offline. This domain impersonates the Pudgy Penguins brand, a popular NFT project, to lure unsuspecting users into revealing their private keys or other sensitive information.
Analysis indicates that pudgy.social was created on April 27, 2026, and is registered through Sav.com, LLC. The domain resolves to the IP address 104.21.32.69. It has been flagged by 12 of 95 VirusTotal vendors, indicating a significant level of suspicion among security professionals. The domain appears on 1 security blocklist, further corroborating its malicious nature. The page title, 'Claim Your $PENGU | Pudgy Penguins,' suggests that the phishing campaign is designed to exploit the popularity of the Pudgy Penguins NFT project, potentially leading users to believe they are participating in a legitimate promotion or transaction.
Currently, the domain pudgy.social is offline, which may indicate that the operators have temporarily ceased their phishing activities or that the domain has been taken down by authorities or security services. However, the domain remains a high-risk entity and should be monitored for any signs of reactivation. Organizations and individuals are advised to exercise extreme caution and avoid interacting with this domain. Security teams should block access to this domain and educate users about the dangers of crypto drainer phishing, particularly those who are involved with or interested in the Pudgy Penguins NFT project.
18 · datasets with records / 13 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/pengutgStored page referenceIoC extraction recorded 2026-07-29 01:58:35 UTC
2 · external source matches
Sav.com, LLC · 104.21.32.69 · DNS, TLS and retained responses
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.
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.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
beau.ns.cloudflare.comtara.ns.cloudflare.comLocation describes the IP network.
1896f36ade3c39aa1dafb6376b0814c22ce306445c77237687a2aec3b25117ceSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
الملاحظات المخزنة المتعلقة بالمقارنة بين برامج الزحف والمتصفح لهذا المضيف، بالإضافة إلى فحص مباشر للبصمة الرقمية لأنظمة توزيع حركة المرور على غرار «كيتارو».
cloudflareملاحظة خاصة بالماسح الضوئي: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://pudgy.social/; server=cloudflare
1 · outbound report records
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
غير معروف→redirected
http_redirect
redirected→غير معروف
probe_inconclusive
غير معروف→redirected
http_redirect
redirected→غير معروف
probe_inconclusive
غير معروف→redirected
http_redirect
redirected→غير معروف
probe_inconclusive
غير معروف→redirected
http_redirect
redirected→غير معروف
probe_inconclusive
غير معروف→redirected
http_redirect
redirected→غير معروف
probe_inconclusive
غير معروف→redirected
http_redirect
redirected→غير معروف
probe_inconclusive
غير معروف→redirected
http_redirect
redirected→غير معروف
probe_inconclusive
غير معروف→redirected
http_redirect
redirected→غير معروف
probe_inconclusive
غير معروف→redirected
http_redirect
redirected→غير معروف
probe_inconclusive
غير معروف→redirected
http_redirect
redirected→غير معروف
probe_inconclusive
redirected→غير معروف
stale_current_evidence
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
redirected→غير معروف
probe_inconclusive
غير معروف→redirected
http_redirect
redirected→غير معروف
probe_inconclusive
غير معروف→redirected
http_redirect
غير معروف
probe_inconclusive
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
PD-20260624-9B6942 Recipient: abuse-trusted.savcom@in.wixanswers.com 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 (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. 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.
Recovery steps, reporting contacts and complaint drafts
إذا أدخلت بيانات اعتماد الحساب أو المعلومات الشخصية أو معلومات الدفع أو قمت بتنزيل ملف من هذا النطاق، فاتخذ إجراءً فوريًا. فيما يلي موارد لمساعدتك في الإبلاغ عن الحادث وحماية نفسك.
حدد بلدك للحصول على الاتصالات الرسمية المتعلقة بالجرائم الإلكترونية أو إنشاء مسودة شكوى →.
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 ↗
pudgy.social)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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
تحليل التهديدات باستخدام قائمة الحظر المخزنة، وWHOIS، وDNS، وأدلة الفحص العامة
امسح الآنأرسل النطاقات المشبوهة إلى قاعدة بيانات التهديدات الخاصة بنا — ساهم في حماية المجتمع
إبلاغتقارير التصيد الاحتيالي الأخيرة وتغييرات التوفر الملحوظة
مراقبةراقب التهديدات في الوقت الفعلي أو اعترض على هذا الإدراج إذا كنت تعتقد أنه إنذار كاذب
يقدم هذا التقرير أحدث الأدلة المخزنة المتاحة لـ PhishDestroy. يتم عرض الطوابع الزمنية للمصدر حيثما كان ذلك متاحًا؛ يمكن أن تتغير أحكام التوفر والبائعين بعد التجميع.
عرض الموقع الذي تم التقاطه عنوان الصفحة “Claim Your $PENGU | Pudgy Penguins”.
اعتبارًا من 2026-09-28 02:33:54 UTC، كان لدى pudgy.social اكتشافات من محركات الأمان 14.
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
إذا كنت تعتقد أن هذه القائمة غير دقيقة، تقديم استئناف. للتعرف على منهجيتنا، قم بزيارة صفحة الأسئلة الشائعة.