VirusTotal
10 / 89 engine detections
Відкрити звіт“Site not found · GitHub Pages”
підробка під Amazon: devadharsha-k.github.io — Контент недоступний (HTTP 404). Зведення доказів: VirusTotal 10/89 (alphaMountain.ai, Emsisoft, Forcepoint…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
10 / 89 engine detections
Відкрити звітШкідливий
Відкрити звітno community references
Відкрити звітprovider verdict: clean
Відкрити звітNo threat flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
devadharsha-k.github.io is a phishing page that impersonated Amazon. It was hosted on a personal GitHub Pages subdomain and aimed at Amazon shoppers. PhishDestroy first detected it on 2026-09-06. The site has been offline since 2026-09-11 and was still dead when last checked on 2026-10-19, with nothing served at its root.
Amazon impersonation pages copy the retailer's sign-in or account-verification screens. Victims usually arrive through fake order, delivery or account-suspension messages. Anything typed into the form goes to the operator, including the email and password, often the one-time code, and sometimes card or billing details. With that, the attacker can take over the Amazon account, place orders and reuse the password elsewhere. The page title now reads "Site not found · GitHub Pages," which is GitHub's default for a removed page, while our classification is Amazon impersonation.
On 2026-09-11, 10 of 89 VirusTotal engines flagged the domain. The vendors included alphaMountain.ai, Emsisoft, Forcepoint ThreatSeeker, G-Data, Gridinsoft, Lionic, Netcraft and PrecisionSec. That is a modest share of engines, but it comes from a spread of independent vendors, including the anti-phishing specialist Netcraft. urlscan.io returned a malicious verdict and detected Amazon branding on the page. The domain is listed on the PhishDestroy blocklist.
The page lived on github.io, GitHub's free static hosting. The domain is registered through GitHub, Inc., and the operator only needed a throwaway account name rather than a domain of their own. Traffic was served from 185.199.108.153 on Fastly's network in the US, the CDN that fronts GitHub Pages. That borrowed reputation helps such pages slip past filters that trust GitHub. The page went dark five days after we first detected it.
If you entered your Amazon credentials on this page, change your Amazon password right away and sign out of all devices. Turn on two-step verification, and change the password on any other account that used the same one. Check your Amazon order history, saved addresses and payment methods for anything you did not add. If you entered card details, ask your bank to block the card and dispute any unfamiliar charges. Defenders should block this subdomain and search mail and proxy logs for Amazon-themed lures pointing to github.io hosts.
Репутація Edge-IP не пов’язана з цим доменом.
Location describes the IP network.
71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84github.comgithub.iogithubusercontent.comSaved 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 devadharsha-k.github.io · checked Sep 6, 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.
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
http_no_content
Невідомо→inactive
hosting_placeholder · placeholder_page
Невідомо→inactive
hosting_placeholder · placeholder_page
Невідомо→inactive
hosting_placeholder · placeholder_page
Доступний→Недоступно
9→10
8→9
7→8
Доступний
No threat flag
View source10/89 engine detections
View sourcedevadharsha-k.github.io
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
devadharsha-k.github.io
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 ↗
devadharsha-k.github.io)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.