VirusTotal
7 / 92 engine detections
Відкрити звіт“Log in to your PayPal account”
крадіжка облікових даних: securepaypalcard.com — Неперевірений. Зведення доказів: VirusTotal 7/92 (Bfore.Ai PreCrime, Emsisoft, Fortinet, Gridinsoft…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
7 / 92 engine detections
Відкрити звітШкідливий
Відкрити звітThreat flag recorded
Відкрити звітDBL_PHISH
Шкідливий
Відкрити звіт1 community reference
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
securepaypalcard.com is a credential phishing page posing as PayPal, built to capture the login details of PayPal account holders. The domain name pairs "secure" with "paypal" and "card" to look like an official payment or card service. PhishDestroy first flagged it on 2026-10-13. As of 2026-10-19 the domain still resolves, but the phishing content is unreachable, so it can be reloaded at any time.
The page is titled "Log in to your PayPal account" and presents a copy of PayPal's sign-in screen. Victims usually arrive through an email or text claiming a card problem, a limited account or a payment that needs confirming. Whatever they type, typically the email address and password and sometimes a one-time code, goes straight to the operators. With that access they can log in to the real account, send money, change contact details and use any linked cards or bank accounts.
Seven of 92 VirusTotal engines flagged the domain on 2026-10-13: Bfore.Ai PreCrime, Emsisoft, Fortinet, Gridinsoft, Kaspersky, Netcraft and Webroot. Google Safe Browsing lists it under SOCIAL_ENGINEERING, so browsers that use it should show a warning. urlscan.io rated the page malicious and detected the PayPal brand on it, Spamhaus lists the domain in its DBL as DBL_PHISH, and it appears in one AlienVault OTX pulse. These independent sources agree on PayPal phishing, even though most VirusTotal engines had not caught up when it was checked.
The domain was registered on 2026-10-10 through Amazon Registrar, Inc. and was caught three days later. A brand-new domain built around a payment brand fits the short life cycle of phishing campaigns. It is hosted on Amazon's network in the United States. The site uses a free Let's Encrypt certificate, so the padlock in the address bar shows only that the connection is encrypted, not that the site is genuine PayPal.
If you entered details on this site, go directly to PayPal by typing its address yourself and change your password. Change it anywhere else you reused it, and turn on two-step verification. Check recent activity, linked cards and bank accounts, and saved email and phone details for changes you did not make. Report any unauthorized transactions to PayPal and your card issuer quickly. Security teams should block the domain at DNS and the mail gateway, and search mail logs for messages that link to it.
ns-652.awsdns-17.netLocation describes the IP network.
fa263cb603727eb9055a336d14bac3211dd24ca343e1228ee8a9cf32c2db734fwww.securepaypalcard.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.securepaypalcard.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of securepaypalcard.com · checked Oct 13, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→live_content
content_served
Невідомо→live_content
content_served
No flag recorded→Flag recorded
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Threat flag recorded
View source1 community references
View source7/92 engine detections
View sourcesecurepaypalcard.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
securepaypalcard.com
Listed domains receive at least one abuse report; this entry has no retained notification history.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
securepaypalcard.com)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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 і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
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.