Is base-pay-app-ss.pages.dev a scam? TrustSniffer's high-risk assessment: 0/100

Security Alert

Fortinet, Google flagged this site in external intelligence checks, indicating elevated compromise/scam exposure that requires immediate caution.

The website is a hosted web application on a free, shared subdomain platform. Its hostname suggests a payment-application theme built around the word "pay". When its homepage was captured, it presented only a short interstitial warning page titled as suspected phishing, not a functional product interface or any identifiable business content. Its apparent purpose is to look like a payment or wallet-style service, but no product, operator, or service description could be read.

Scam/Impersonation Risk

Contradictory signals are present and decisive. A major browser-safety service currently flags the site for social engineering, and several independent security engines classify it as malicious or suspicious, including two leading security vendors. These detections together make up a confirmed blacklisting. Because the platform's own warning page is what the homepage serves, the site is being actively treated as a phishing risk at the hosting layer as well as by outside reputation sources. No specific legal entity or brand is named, so no conflicting corporate identities were found, and the available evidence does not by itself prove a particular brand is being impersonated. The hostname's payment-app wording is nonetheless typical of lookalike lures aimed at wallet or payment users. Behavioural testing adds support for this reading. The page issued a very large number of outbound background requests, and nearly all page activity was directed at external destinations. It also sent several outbound data submissions and logged repeated script errors. The page structure changed substantially after interaction, which is consistent with a layer swapped in behind a gate. Wallet-connection prompts, clipboard tampering, hidden forms and cross-site password forms were not observed, so no drainer behaviour is confirmed. That absence does not offset the external detections. Evidence:

• Homepage: served a suspected-phishing warning page instead of site content, with a blocked access response.
• Homepage: a major browser-safety service flagged it for social engineering, and multiple security engines flagged it as malicious.
• Behavioural sandbox: heavy external request traffic, repeated outbound submissions, repeated script errors and a large post-interaction page change.
• Behavioural sandbox: no wallet-connection, clipboard-hijack or hidden-form activity detected.

Regulatory Verification Notes

The captured page contained no legal, terms, privacy, licensing or registration disclosures, so no regulatory standing can be attributed to the site. No third-party regulated status was found, and no broker-reputation record matched. The site cannot be tied to any real-world brand or person, and no on-page claim exists to credit. Because the homepage is a warning interstitial and not the site's own content, this is a consequence of the capture. It is not a finding about the operator's disclosure practices. The site runs on a shared subdomain platform, so the platform operator, not an independent registrant, controls the domain registration layer. A valid certificate exists but only confirms an encrypted connection, not who operates the site or whether it is legitimate. Evidence:

• Hosting infrastructure: served from AS13335 (Cloudflare, Inc., US).
• Transport encryption: TLS certificate issued by WE1 (DV, domain validation only), valid to 2026-12-22.
• Homepage: warning text only, with no entity name, license number, or policy pages.

What to Verify Next

The practical step is to treat the site as unvetted and avoid engaging with it. Anyone who received the link through a message, advertisement or social post should confirm independently, through the app store listing or the official website of the payment provider they actually intend to use, whether any such application exists. Official contact channels should be obtained from that independent source, not from this site or from the message that carried the link. If the link claims to represent a known brand, report it to that brand's security team and to the hosting platform's abuse process. A site owner who believes the listing is mistaken should check whether the site has been compromised before requesting a review. Evidence:

• Homepage: reachable only as a phishing warning page, with no functioning product to validate.
• Hostname: a payment-app naming pattern that does not match any identified brand.
• Reputation sources: current malicious and social-engineering classifications, which must clear before any engagement.

Summary Verdict

The site carries an elevated risk posture. Confirmed external threat detections, corroborated by the hosting platform's own phishing warning and by anomalous outbound behaviour, outweigh every neutral or positive technical attribute. The identity of the operator is unknown, and nothing in the evidence supports a legitimacy conclusion.

Infrastructure Integrity

The site is delivered through a recognised CDN and web application firewall, and all observed addresses are edge servers, so the origin host cannot be seen and independent hosting verification is not possible. The bot-challenge layer also limited what could be captured from the homepage. Protective infrastructure is a mitigating factor only. It does not offset the external threat detections and cannot be treated as evidence of legitimacy.

Closing Assessment

The site should not be used for login, credential entry, wallet connection, or any payment or financial action. Read-only viewing is the most that is appropriate, and no files should be downloaded from it. Any credentials or funds already submitted should be treated as exposed: change affected passwords, review account activity, and notify the relevant financial provider.