VirusTotal
9 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Telegram”
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@vpspay.cloud.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
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.
9 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
8 threat-system alerts
ReportAlerts refer to the preserved scan. They do not describe the current state of the site.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
80/100
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Nextron YARA rules | telegram-premiuma.com/bdd0fb44597a99577acdff567f900db4899a8a2dc035627552f10c061b7d7be0/ihd3lyv/bc07wufawyw8.js |
malware | Unique code from Jetriz, Swid & Jeniva of the Tetris framework |
| Nextron YARA rules | telegram-premiuma.com/bdd0fb44597a99577acdff567f900db4899a8a2dc035627552f10c061b7d7be0/ihd3lyv/pjuylvc7wvrs.js |
malware | Unique code from Jetriz, Swid & Jeniva of the Tetris framework |
| Nextron YARA rules | telegram-premiuma.com/bdd0fb44597a99577acdff567f900db4899a8a2dc035627552f10c061b7d7be0/ihd3lyv/gcfn9ezg0p5w.js |
malware | Unique code from Jetriz, Swid & Jeniva of the Tetris framework |
| Nextron YARA rules | telegram-premiuma.com/bdd0fb44597a99577acdff567f900db4899a8a2dc035627552f10c061b7d7be0/ihd3lyv/fotrem5ns4qc.js |
malware | Unique code from Jetriz, Swid & Jeniva of the Tetris framework |
| Nextron YARA rules | telegram-premiuma.com/bdd0fb44597a99577acdff567f900db4899a8a2dc035627552f10c061b7d7be0/ihd3lyv/ibyw3cqxgxog.js |
malware | Unique code from Jetriz, Swid & Jeniva of the Tetris framework |
| Nextron YARA rules | telegram-premiuma.com/bdd0fb44597a99577acdff567f900db4899a8a2dc035627552f10c061b7d7be0/ihd3lyv/kompuwfks7is.js |
malware | Unique code from Jetriz, Swid & Jeniva of the Tetris framework |
| OpenDNS | telegram-premiuma.com |
phishing | Phishing Block |
| DNS4EU | telegram-premiuma.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.
telegram-premiuma.com returned HTTP status 302 on 2026-10-01 according to the recorded HTTP check. The domain was first observed on 2026-09-05, and its registration date is recorded as 2026-08-19.
The HTTP check on 2026-10-01 recorded status 302 for telegram-premiuma.com. A PhishDestroy internal listing was recorded, and the domain first appeared on 2026-09-05. VirusTotal recorded 9 detections across 89 scanners on 2026-09-18. OTX recorded 4 pulses on 2026-09-11. The registrar is NICENIC INTERNATIONAL GROUP CO., LIMITED, and the SSL issuer is Let's Encrypt / YE2 as scanned on 2026-09-05.
The PhishDestroy listing and the VirusTotal count on 2026-09-18 were recorded on different dates, so they reflect separate observation points rather than one combined snapshot. OTX pulses on 2026-09-11 and the HTTP status on 2026-10-01 likewise come from different checks, which limits direct comparison. The registration date of 2026-08-19 precedes the first observation on 2026-09-05, giving a recorded sequence for the domain.
Reviewers should retain the dated records for telegram-premiuma.com so later checks can be compared against the 2026-10-01 HTTP status and the 2026-09-18 VirusTotal count. Any new observation should be logged with its own date before conclusions are drawn. During review, avoid submitting sensitive information to the domain until its status is independently confirmed.
21 · datasets with records / 10 · 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.
0 · external source matches
NICENIC INTERNATIONAL GROUP CO., LIMITED · 144.31.53.157 · DNS, TLS and retained responses
rocco.ns.cloudflare.comzita.ns.cloudflare.comLocation describes the IP network.
03204437a1b6c17622fae99069e2826cd3e6352ce779d37a47fee472b1d61cb8Saved 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 telegram-premiuma.com · checked Sep 5, 2026
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
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: redirect: raw=redirect_302; http=302; via=https_proxy; location=https://www.google.com
No live-check result has been retained.
1 · outbound report records
144.31.53.157.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
redirected→Unknown
stale_current_evidence
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
redirected
http_redirect
7→8
Reachable
13 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-20260905-603162 Recipient: abuse@vpspay.cloud Registrar: NICENIC International Group Co., Limited (Hong Kong (China)) Policy Violations: “Services may be used only for lawful purposes… fraud, abuse and illegal activity prohibited. Violations may result in immediate suspension.” + dedicated abuse handling and takedown Applicable Laws: Crimes Ordinance Cap.200 (Fraud), Theft Ordinance Cap.210 §16A (fraud by deception), Personal Data (Privacy) Ordinance Cap.486
Recovery steps, reporting contacts and complaint drafts
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select 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 ↗
telegram-premiuma.com)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
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “Telegram”. Apparent target: Telegram.
VirusTotal detections for telegram-premiuma.com: 9 (2026-09-18 02:09:32 UTC).
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.
submit an appeal or review the FAQ page.