The domain bck2.pbkd198.ru displays a ScreenConnect remote support portal prompting visitors to enter a secure connection code. If you entered a code here, disconnect any active remote sessions immediately.
Page title: “ScreenConnect Remote Support Software”
More about the sources
Recorded security signals
Stored VirusTotal result: 5/92 engines flagged. Malicious: 3. Suspicious: 2. Analysis time (as stored): 2026-11-19 09:15 UTC. Retrieved (as stored): 2026-11-19 21:43 UTC. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
ABUSE NOTICE · 24H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at . The recorded recipient is abuse-ams@v-sys.org. The latest stored availability evidence still shows the domain reachable; 2 days 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.
Elapsed since first report
2 days
Reports sent
1
Latest case ID
PD-2ABB228CDA0BFE53493D
Current status
HTTP 200 at latest stored check
Analysis
Domain summary
PhishDestroy first recorded bck2.pbkd198.ru on 2026-11-19. Stored VirusTotal result: 5/92 engines flagged. Malicious: 3. Suspicious: 2. Analysis time (as stored): 2026-11-19 09:15 UTC. Retrieved (as stored): 2026-11-19 21:43 UTC. Risk: critical (evidence score 85/100). Registrar: RU-CENTER-RU. Status: Last known active. Hosting: SOLLUTIUM EU Sp z.o.o. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
URLScan capture · 2026-11-19 21:10 UTC · SHA-256 1dcf4650…7647754
PhishDestroy analysis, reviewed version
ScreenConnect secure code interface
The page presents a dark blue and teal gradient background that mimics the standard ScreenConnect remote support interface. In the top left corner, it displays the "ScreenConnect" brand name beside its logo icon. Centered on the screen is a white box titled "Secure Code" featuring an empty text entry field and a gray button with a right-arrow symbol. The layout invites visitors to type in a remote support code to establish a connection. urlscan classified the page as malicious, and 5 of 92 engines on VirusTotal flagged it on 19 Nov 2026, with Webroot, SOCRadar and alphaMountain.ai among them.
Remote access risks and telemetry
PhishDestroy's evidence score for it is 50/100 (high). Because the site was still reachable on 19 Nov 2026 at 22:11 UTC, entering a code into this prompt can grant unauthorized remote access to your device or network. Security vendors flag the URL because it exploits trusted remote support branding to trick users into connecting. Always verify support addresses directly with your IT provider instead of entering codes into unfamiliar links.
Recommended precautions and response
If you reached this page from an unverified link or communication, close the browser tab immediately and do not input any codes. For individuals who already entered a support code, check your system for newly installed remote management software, terminate any active support connections, and run a complete antivirus scan. Always navigate to support tools using official bookmarks or known corporate channels.
Source evidenceVirusTotal 5 / 925 sources
SourceResultRecorded · UTCOpen
VirusTotal
5 / 92 engine detections
Analysis:
Open report VirusTotalOriginal source recordObserved: 11 fields
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
AI title
bck2.pbkd198.ru — ScreenConnect secure code login
AI description
bck2.pbkd198.ru displays a ScreenConnect remote access portal requesting a code, flagged by urlscan and 5 VirusTotal engines. Do not submit data.
AI summary
ScreenConnect secure code interface The page presents a dark blue and teal gradient background that mimics the standard ScreenConnect remote support interface. In the top left corner, it displays the "ScreenConnect" brand name beside its logo icon. Centered on the screen is a white box titled "Secure Code" featuring an empty text entry field and a gray button with a right-arrow symbol. The layout invites visitors to type in a remote support code to establish a connection. urlscan classified the page as malicious, and 5 of 92 engines on VirusTotal flagged it on 19 Nov 2026, with Webroot, SOCRadar and alphaMountain.ai among them. Remote access risks and telemetry PhishDestroy's evidence score for it is 50/100 (high). Because the site was still reachable on 19 Nov 2026 at 22:11 UTC, entering a code into this prompt can grant unauthorized remote access to your device or network. Security vendors flag the URL because it exploits trusted remote support branding to trick users into connecting. Always verify support addresses directly with your IT provider instead of entering codes into unfamiliar links. Recommended precautions and response If you reached this page from an unverified link or communication, close the browser tab immediately and do not input any codes. For individuals who already entered a support code, check your system for newly installed remote management software, terminate any active support connections, and run a complete antivirus scan. Always navigate to support tools using official bookmarks or known corporate channels.
Is bck2.pbkd198.ru an official ScreenConnect website?
No, it is flagged by urlscan and 5 VirusTotal engines. Official remote support tools are hosted on corporate infrastructure rather than on bck2.pbkd198.ru, which was registered on 10 Apr 2026 through RU-CENTER-RU.
What happens if I entered a secure code on bck2.pbkd198.ru?
Entering a code into the "Secure Code" prompt on this page may allow unauthorized actors to initiate a remote support session on your device. You should immediately close any resulting connections, check for unauthorized remote software, and run a full security scan.
How can I safely access my support session?
Always navigate to remote support portals by typing your organization's known URL directly into your browser or using official bookmarks. Avoid entering codes into unverified links or unfamiliar domains that appear online.
IP Reputation85.137.56.1620/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worseThis IP address has not been reported to the abuse database yet, but the domain itself is recognized as phishing.0 reportschecked 2026-11-20
Certificate fingerprintd1bc7d451cee5f3a70e0797c6406de3a09fa1a8c7e0622928a6719b6ac558a42Certificate names · 4 SANs
auth.autz724.ru
bck2.pbkd198.ru
bck2.pbkt276.ru
m.mob724.org
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: Resolved
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-11-21 11:12 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-22 11:11 UTClast content: 2026-11-22 11:11 UTC
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.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-19 23:04 UTC.
Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
4 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+223 d 2 h
Added to PhishDestroy+11 h 55 min
First abuse report sent+1 h 53 min
Reported 223 d 15 h after registration
Abuse report sent
PD-2ABB228CDA0BFE53493D · Receipt 85351
abuse-ams@v-sys.org
+2 min
URLScan
Page captured
+1 h 50 min
Added to PhishDestroy
bck2.pbkd198.ru
+11 h 55 min
VirusTotal
5/92 engine detections
How we investigate & report
Public scans, evidence and abuse channels
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.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches6
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including bck2.pbkd198.ru)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
About this reportSources, observation dates and corrections
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.