Is naruflix.pages.dev a scam? TrustSniffer's high-risk assessment: 5/100

Security Alert

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

This is a project hosted on a shared, free developer-platform subdomain, and its name suggests a streaming or media theme. When the site was captured, visitors received a hosting-provider interstitial titled as a suspected-phishing warning in place of any readable site content. Its purpose and business model therefore cannot be established from the page itself. The deployment is recent, and its public presentation is minimal.

Scam/Impersonation Risk

Contradictory signals are present, and they drive the cautionary posture of this assessment. The site is currently on a confirmed blacklist: multiple independent security engines classify it as malicious, and two of the better-known commercial security vendors are among them. The hosting platform's own challenge page labels the site as suspected phishing, which is consistent with those detections. No conflicting legal identities and no explicit brand-impersonation evidence were observed. The risk therefore rests on the reputation and phishing-warning signals, not on a demonstrated lookalike of a named brand. Behavioural testing showed no wallet-connection prompts, clipboard tampering, hidden forms or credential posts to outside parties, so the available evidence does not show how the site would harm a visitor. However, a very large share of page activity went to outside domains, with a heavy volume of background requests and repeated script errors. That pattern fits a thin or unstable front end that loads most of its content from elsewhere. Combined with the detections, it supports treating the site as unsafe for any login, credential entry or payment. Evidence:

• Homepage capture returned a Cloudflare-served phishing-warning interstitial in place of site content.
• Several independent threat-intelligence engines flag the domain as malicious or suspicious, including two prominent commercial vendors.
• Behavioural runs recorded 26 external background requests, about 95% of activity directed outside the site's own domain, and 20 console errors.
• Domain first observed 2024-12-07 (~1.9 years old); 4 archive snapshots spanning 2024–2025 (2 years tracked), a thin history that offers no established record of legitimate use.

Regulatory Verification Notes

The site presents no identifiable operator, legal entity, licence or registration details, and its hosting arrangement offers no independent anchor for ownership. This is ownership opacity. It is a transparency gap that raises the cost of accountability if something goes wrong. It is not an identity contradiction, because no competing legal names were found. Nothing links the site to a regulated or recognised brand, and no third-party broker or regulatory-reputation entry matched it. The site should not be treated as a supervised or licensed service on any basis. Its shared-platform subdomain also means it has no independent domain identity of its own. Evidence:

• No operator, company or licensing information could be tied to the site; the only readable page content was the platform's warning interstitial.
• Served from AS13335 (Cloudflare, Inc., US).
• TLS certificate issued by WE1 (DV, domain-validated only), valid to 2026-12-16. This confirms encryption, not the operator's identity.

What to Verify Next

Before any engagement, confirm who operates the site through a channel independent of the site, and ask the person who supplied the link where it originated. Anyone who received the link through a message, advertisement or social post should check it against the official presence of the service it claims to represent. Official contact channels should be confirmed through an offline or separately sourced route. Access should be limited to passive viewing from an isolated, up-to-date browser, and nothing should be downloaded from the site. If the site is believed to belong to the user's own organisation, the hosting project owner should be contacted to review the flagging. Evidence:

• The site sits on a shared subdomain of a developer-hosting platform, so no standalone domain registration points to an accountable operator.
• The security engines' detections are current and remain unresolved.
• Behavioural testing showed no wallet or credential-capture activity, which is why passive viewing is the only use the evidence tolerates.

Summary Verdict

The evidence converges on an elevated-risk, clearly cautionary posture. Active third-party threat detections and a platform-level phishing warning outweigh the neutral technical hygiene of the deployment. The operator's identity is unconfirmed, and the site cannot be considered trustworthy for any sensitive interaction.

Infrastructure Integrity

The site is delivered through Cloudflare's CDN and WAF, and all four observed addresses (two IPv4 and two IPv6) are Cloudflare edge servers. The origin server was not observable, so the actual hosting location cannot be verified independently, and content could be swapped without a visible change in network posture. The CDN, bot-challenge layer and valid encryption are mitigating factors only. They do not offset the external detections and do not demonstrate legitimacy.

Closing Assessment

The site should be treated as unsafe for login, credential entry, financial transactions and downloads. If it must be examined at all, it should be viewed read-only from an isolated environment. Any account details already entered should be changed promptly, and the link should be reported to the sender's platform or the security team.