Skip to security report
Analytics Dashboard
Domain security and threat intelligence
access-sc.jp favicon

access-sc.jp

In short

access-sc.jp is a ShopeePay impersonation page detected by PhishDestroy on 2026-09-15. Risk: critical (98/100). Status: Last known active. Hosting: XServer Cloud Inc. VirusTotal: 12/91 engines flag it. Do not enter credentials or connect a wallet.

“Access Shopee Connect”

Resolved IP
85.131.243.103
Registered
Feb 5, 2025
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 12/91 Automated brand label: ShopeePay
OTX: 5 refs Sep 15, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 12. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
12 / 91
engine detections
Google Safe Browsing
No threat flag
OTX
5
community references
Page captures
9
open gallery
Domain age
624 days
Source evidenceVirusTotal 12 / 91 · OTX 5 references 6 sources

VirusTotal

12 / 91 engine detections

Open report

OTX

5 community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing
View full Cloudflare Radar report

Analysis

Critical
VirusTotal
12 / 91
OTX
5 community refs
Page captures
9
Page captures Source results Registration record

PhishDestroy threat report

Overview

access-sc.jp is a phishing page that impersonates Shopee under the title 'Access Shopee Connect'. It targets Shopee users, especially sellers who would expect a portal with that name. PhishDestroy first flagged it on 2026-09-15. On 2026-10-19 the site was still online and serving its phishing content.

How the scam works

Impersonation pages like this copy the look and wording of a trusted brand. Victims arrive through a link in a message, ad or search result, and the 'Access Shopee Connect' title makes the page look like an official Shopee entry point. Anything typed into it, such as usernames, passwords, one-time codes, contact details or payment information, goes straight to the operators. A stolen Shopee account can be used to place orders, change payout details on a seller account, or run further scams that look like they come from a trusted shop.

Evidence

On 2026-09-25, 12 of 91 VirusTotal engines flagged the domain, including BitDefender, Kaspersky, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF and alphaMountain.ai. That is a minority of engines, but the vendors behind those flags are well-established and independent of each other. urlscan.io rated the page malicious and recognized Shopee as the brand being imitated. The domain also appears in 5 AlienVault OTX threat pulses and is on the PhishDestroy blocklist.

Infrastructure

The domain was registered on 2025-02-05, more than a year and a half before PhishDestroy detected it. A long gap like this often means a domain was held in reserve before being put to use. The site runs on XServer Cloud Inc. in Japan at 85.131.243.103. A Japanese domain on Japanese hosting helps it look credible to local Shopee users. Its Let's Encrypt certificate gives it the browser padlock, which proves nothing about who runs the site.

What to do

If you entered your Shopee login on this page, change your password right away from the official app or by typing Shopee's address yourself. Turn on two-factor authentication and sign out of all other sessions. Sellers should also check their bank and payout settings, linked emails and any recent listings for changes they did not make. If you entered card details, contact your bank to block the card, and report the incident to Shopee support. Security teams should block access-sc.jp and the hosting address above, and watch for similar 'Shopee Connect' lookalike domains in mail and web traffic.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-09-15T13:54:35Z

Observed: · Retrieved:

Uuid
01a0a558-fb58-76eb-9840-06fb11a66f5f
Final url
https://access-sc.jp/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://access-sc.jp/",
        "from": "http://access-sc.jp/",
        "status": 307
    }
]
Ip
85.131.243.103
Ptr
x85-131-243-103.static.xvps.ne.jp
Contacted domains
[
    "region1.google-analytics.com",
    "www.googletagmanager.com"
]
Contacted IP addresses
[
    "216.239.32.36",
    "142.251.127.97",
    "85.131.243.103"
]
Asns
[
    "15169",
    "131965"
]
Countries
[
    "US",
    "JP"
]
Document hash
b1c4ac8bfd4888d60252f98a5b9b9c07dad7ef6eef4977fc511eacb2d152a81e
Script hashes
[
    "466fa0a47d3850ee45e19e3a847c6762a7449d6a5b35374a84399c399077ba9c"
]
Globals
[
    "gtag",
    "dataLayer",
    "google_tag_data",
    "google_tag_manager",
    "onYouTubeIframeAPIReady",
    "gaGlobal",
    "__reactRouterVersion"
]
Cookies
[
    "_ga",
    "_ga_LZ4DV07RNM"
]
Tls
{
    "san": [
        "access-sc.jp"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "access-sc.jp",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-07T17:21:01Z",
    "valid_from": "2026-08-09T17:21:02Z"
}
Domain age days
579
Apex age days
579
Tls age days
36
Tls valid days
89
Requests
9
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 92,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "shopee"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Shopee"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=UTF-8",
    "x-powered-by": "Express",
    "x-frame-options": "DENY",
    "x-content-type-options": "nosniff"
}
Cloudflare Radar · 2026-09-15T13:56:47Z

Observed: · Retrieved:

Uuid
686086c1-e536-4143-823d-6a3987ec932f
Final url
https://access-sc.jp/
Status
200
History
[
    {
        "url": "https://access-sc.jp/",
        "status": 200
    }
]
DOM structure hash
9292d91d86728958fadc7e0efc6b930b7de1725d8a75e6dde9e5e37c56983d7b
Document hash
b1c4ac8bfd4888d60252f98a5b9b9c07dad7ef6eef4977fc511eacb2d152a81e
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "access-sc.jp",
        "type": "A",
        "value": "85.131.243.103"
    }
]
Dnssec valid
false
Ip
85.131.243.103
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "created": "2025-02-05T00:00:00Z",
    "updated": "2026-03-31T07:45:26Z",
    "expires": "2027-02-28T00:00:00Z",
    "nameservers": [
        "dns01.muumuu-domain.com",
        "dns02.muumuu-domain.com"
    ]
}
VirusTotal · 2026-10-14T10:23:48Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 56,
    "malicious": 1,
    "suspicious": 0,
    "undetected": 35
}
Vendor labels
{
    "Gridinsoft": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "BitDefender": "misc",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
First seen
2025-02-16T16:04:22Z
DNS records
[
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns01.muumuu-domain.com"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "postmaster.access-sc.jp",
        "value": "dns01.muumuu-domain.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns02.muumuu-domain.com"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "85.131.243.103"
    }
]
Dns at
2026-10-14T10:28:24Z
Jarm
27d40d40d00040d00042d43d000000d2e61cae37a985f75ecafb81b33ca523
Certificate
{
    "san": [
        "access-sc.jp"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6683b7486a55ed330d6bde972025c290aa",
    "sha256": "da24ab0d570e943c6c526566df67476a50c9423c889a93e4a1433325f2fe0c10",
    "subject": "access-sc.jp",
    "valid_to": "2027-01-07T01:32:41Z",
    "valid_from": "2026-10-09T01:32:42Z"
}

Questions about access-sc.jp

Is access-sc.jp legit?

No. PhishDestroy classifies access-sc.jp as a ShopeePay impersonation page (risk: critical, 98/100); it was first detected on 2026-09-15. VirusTotal: 12/91 engines flag it. Treat the site as unsafe.

Is access-sc.jp safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on access-sc.jp. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used access-sc.jp?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 9 captures

Primary capture 1 / 9
SourcePrimary capture
Recorded2026-09-15 13:55 UTC
StateStored capture
Position1 / 9
Open capture Wayback Download

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Shopee report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 15, 2026
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
RegistrationCreated Feb 5, 2025 — Expires Feb 28, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 15, 2026
DOM Analysisanalyzed Sep 15, 2026score 98/1001 brand signal
Submitted URLhttp://access-sc.jp/
Favicon Hash
Observed page title
Access Shopee Connect
Automated brand references
ShopeePay
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 76 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
85.131.243.103
Network ASN
AS131965
Organization
XServer Cloud Inc.
Observed location
Osaka, JP
Server header
nginx

Nameservers 2

  • dns01.muumuu-domain.com
  • dns02.muumuu-domain.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-09 01:32:42
Valid until
2027-01-07 01:32:41
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-11 01:03:38 UTC
Collection source
PhishDestroy collector
Certificate fingerprintda24ab0d570e943c6c526566df67476a50c9423c889a93e4a1433325f2fe0c10
Certificate names · 1 SAN
  • access-sc.jp

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 85.131.243.103rapiddns.io

Latest Classified Outcome 2026-10-22 10:24:37 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-22 10:24:37 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:24:37 UTC last content: 2026-10-22 10:24:37 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.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos
VIPRE

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of access-sc.jp · checked Sep 15, 2026

60
Needs Work
Performance
FCP
5.62s
First Contentful Paint
LCP
7.18s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
7.28s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

Page titles differ

alive_content: raw=ok; http=200; via=https_proxy; server=nginx

Browser
Access Shopee Connect
Crawler
ASC（Access Shopee Connect）| 株式会社NEXT
access-sc.jp
Saved result
Cloaked / Filtered
Stored observation history21

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 16
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    live_content

    content_served

  16. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. AlienVault OTX

    5 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    12/91 engine detections

    View source
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    access-sc.jp

    View source

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 12 det. ChainPatrol URLQuery Scamadviser 80 trust SSL Labs Stored certificate dates valid CF Radar Malicious OTX 5 refs WOT Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 access-sc.jp)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/access-sc.jp"
  title="PhishDestroy threat report for access-sc.jp"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>