---
title: "Is runc-12b.pages.dev a Scam? Risk Report, Score 0/100"
source: TrustSniffer
type: Website trust & fraud report
subject: "runc-12b.pages.dev"
verdict: "Critical Risk"
trust_score: 0
classification_confidence: 75
canonical_url: https://trustsniffer.com/report/runc-12b.pages.dev
assessed: 2026-11-13
---

# Is runc-12b.pages.dev a scam? TrustSniffer's critical-risk assessment: 0/100

## Verdict


**Verdict: Critical Risk, trust score 0/100.** runc-12b.pages.dev shows critical-risk indicators.

External threat listings named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

Labels: Sensitive Interaction Risk, Governance Risk
- **Sensitive Interaction Risk:** This label is given when the overall risk is high. The captured page did not ask for a password, card number or other sensitive details; if it ever does, entering them here could be unsafe.
- **Governance Risk:** A registration check came back incomplete: as a site on pages.dev, this address has no registration record of its own (the platform's domain is registered, not the site). That is a gap in what could be looked up, not a sign that ownership is hidden, and it does not say who runs the site.

Assessed 2026-11-13 by automated analysis. Evidence confidence 75%.

| Field | Value |
| --- | --- |
| How the site describes itself | A Solana token page offering holders a claim on 50% of protocol trading fees, requiring wallet connection, transaction approval and a SOL fee, with a 14-day expiry and no verifiable operator, contract address, or fee figures. |

## Evidence status and limitations


Evidence completeness: Complete

_This says whether every check on the site was recorded as finished. All of them were._

- External threat sources confirmed a listing for this site when the evidence was captured (VirusTotal, a threat-intelligence listing from a feed TrustSniffer monitors (phishing, the site itself as the source, last seen 2026-10-25)). On its own it would limit the score to at most 24; the score is lower because of the other findings below.
- The real-world operator identity was not independently verified.

### How to read these numbers

A trust score of 0 means the risk evidence outweighed every trust signal by more than the 0 to 100 scale can show. It rates the evidence found, not the probability that the site is a scam.

Evidence confidence (75%) measures how much of TrustSniffer's evidence set this site produced: the page reading, the browser sandbox, the web archive, the registration record and the reputation services. It falls when a check returns nothing, as listed above, and it does not change the score.


## At a glance

The checks that decide most of this verdict.

| Check | Result | Status |
| --- | --- | --- |
| What limits the score | The findings below (The independent sources ceiling (at most 24) and the threat-listing ceiling (at most 5) also apply, but the findings brought the score lower.) | Watch |
| Malware engines | 4 marked it malicious, 1 suspicious (VirusTotal; Fortinet, Sophos among the engines that flagged it) | Risk |
| Google Safe Browsing | Not listed (Google) | Clear |
| Abuse reports on the CDN edge address | 0% confidence (AbuseIPDB, 0 reports; this is the record of the CDN edge address, not of the server behind it, which was not observed) | Noted |
| First seen | 6 months before capture (Web archive; a site on pages.dev has no registration of its own) | Watch |
| Web archive | Archived since 2026 (2 snapshots; the archive has almost no record of this site, which counted against it) | Watch |
| Certificate | Encrypted connection (Issued by YE2) | Noted |

## The page as captured


![Screenshot of the runc-12b.pages.dev homepage captured during the TrustSniffer assessment](https://trustsniffer.com/outputs/runc-12b.pages.dev/screenshots/first.png)

_What runc-12b.pages.dev served when TrustSniffer captured it on 2026-11-13. The page may look different now._

## Key findings


- Automated classification: Sensitive Interaction Risk, Governance Risk.
- First seen: less than 1 year before capture (web archive; a site on pages.dev has no registration of its own).
- Public web-archive history exists since 2026.
- At least one reputation service TrustSniffer consulted had flagged this domain when the evidence was captured.

## Full analysis


### Security Alert

4 VirusTotal engines, including Fortinet, Sophos, marked this site as malicious; independent sources confirm a listing for this site.


### Overview

This website is a single-page Solana wallet-claim page titled "Fee Distribution", hosted on a free Cloudflare Pages subdomain. It tells visitors that 50% of all trading fees collected by a "$TOKEN" protocol are being distributed to holders in a "first and final distribution", and invites them to connect a wallet and claim a "revenue share". Its apparent purpose is to move visitors through wallet connection and transaction approval, with a SOL fee presented as a step to "verify holdings".


### Scam/Impersonation Risk

Contradictory signals are present, and the site presents critical risk. Four antivirus engines, including the leading vendors Fortinet and Sophos, classed the address as malicious, and a fifth rated it suspicious. A separate threat-intelligence listing places the site in the phishing class in the role of actor, meaning the site is treated as the party carrying out the activity. The two independent sources align, and the listing was last seen on 25 October 2026. No file on the site is described as compromised. The page's own mechanics match the listing. The homepage states that "a small SOL fee will verify your holdings, and right after approval you will receive your tokens". That is a payment-and-approval step placed before any benefit is shown, which is the pattern of a wallet-drainer or claim scam. The urgency is built in: the page says "This is the first and final distribution" and that "Unclaimed rewards expire after 14 days". The headline return is a promise of 50% of protocol fees, yet the page shows only "loading..." for Total Fees Collected, the Holder Pool, Market Cap and Token Price. The distribution history lists one epoch with no date and no pool amount, and the claim flow shows "An Error Occurred" when no wallet is connected. The page also gives no allocation formula, so a visitor cannot tell what the claim would pay out. The sandbox did not observe a wallet-drainer or clipboard-hijack routine. It did record 27 requests sending data to other hosts, 12 of them to destinations TrustSniffer does not recognise, and this data sent elsewhere is a scored finding that counts toward the score. The page's code also raised numerous console errors, another scored finding. These behaviours are not those of an ordinary static claim page.
_A console error is a technical error message that the page's own code reported inside the browser while it ran. It describes how the page is built, and on its own it is not proof that the site is harmful._

Evidence:
- VirusTotal results: 4 engines malicious and 1 suspicious, with Fortinet and Sophos among the malicious verdicts.
- Threat-intelligence listing: phishing class, role actor, last seen 2026-10-25, aligned with the VirusTotal result.
- Homepage: the "A small SOL fee will verify your holdings" instruction, the "first and final distribution" statement and the "expire after 14 days" notice, with every fee and pool figure showing as "loading...".
- Behavioural capture of the homepage: 27 requests sending data to other hosts, 12 of them to destinations TrustSniffer does not recognise, 68.6% of files loaded from other domains, and 14 console errors.

### Regulatory Verification Notes

On the single page read, the site names no operator, legal entity, regulator or licence. The only identity text is the page heading "Fee Distribution", which is a title and not an entity. Of the disclosures expected from a token project, the page does show a reference to "Terms & Privacy Policy" on the connect prompt. On the page read, it shows no contract address, which the page itself acknowledges with the line "No contract address in URL", and it names no team. For a page that asks for a transaction approval and a fee, these are significant gaps. The only fee figure shown is the network gas estimate. No distribution fees, amounts or refund terms are stated on the page read. Identity remains unverified, and nothing independently connects the page to any real protocol or person. The address is a subdomain on a free hosting platform, so the site has no registration of its own.

Evidence:
- Registration record: the address is a subdomain of the pages.dev hosting platform, first seen 187 days before capture, so it has no registration record of its own.
- Web archive: 2 snapshots from 2026-05-10 to 2026-06-03, a 24-day span.
- Hosting network: served from AS13335 (Cloudflare, Inc., US).
- Transport encryption: a TLS certificate issued by YE2 at domain-validated (DV) level, valid to 2027-01-08.
  _A TLS certificate is what puts the padlock and https:// in your browser and encrypts the connection. "YE2 at domain-validated" is the name of the authority that issued it. DV (domain validated) means the issuer only confirmed who controls the domain name, not which person or company runs the site. "Valid to" is the date it expires._

### What to Verify Next

Any claim that a "$TOKEN" fee distribution exists should be confirmed through the project's official channels, reached independently of this page. The page does not name the token, so the first step is to establish which token it refers to. The token's contract address should be obtained from the project's established channels and checked on a Solana block explorer, including whether any fee-distribution programme exists and who controls it. The explorer should also be used to check whether the wallet-approval request matches a known, audited program. A transaction that grants broad permissions in exchange for a "verification fee" should not be treated as a routine claim. Any official support or announcement channel should be confirmed offline or through a source the project is already known to use.

Evidence:
- Homepage: the page says only "$TOKEN" and gives no token name or contract address to check.
- Homepage: the claim flow lists Phantom, Solflare, Backpack and WalletConnect as supported wallets, and asks for approval of a transaction before showing any allocation.
- Homepage: the distribution history shows epoch #01 with no date and no pool amount.

### Summary Verdict

The available evidence supports a critical-risk assessment. Confirmed external listings, a payment-before-benefit claim mechanic, missing operator and contract information, and unexplained outbound network behaviour converge on the same conclusion. The few technical positives observed carry no weight against these findings, and nothing in the evidence supports the page as a legitimate fee-distribution service.


### Infrastructure Integrity

The site is delivered through Cloudflare's network, and every address observed belongs to Cloudflare edge servers. The origin server was not observed. Because the infrastructure is shared by a very large number of unrelated sites, it reflects the hosting choice only and says nothing about the page's operator or intent. The host address's abuse record was checked and showed no reports, but a clean record for shared infrastructure does not offset the findings on the page itself.


### Closing Assessment

The wallet should not be connected to this page, no transaction should be approved, and no SOL fee should be paid to it. Anyone who has already connected a wallet or approved a transaction should review and revoke the token permissions granted, and move remaining assets to a new wallet if there is any doubt.


_Written analysis generated 2026-11-13 by the TrustSniffer Analysis Engine from the evidence in this report._

## What the analysis found

19 findings contributed to this verdict, raised by external reputation, page content, several checks together, history in the web archive, registration and ownership and behaviour in a sandbox.

### 01 External reputation
- 4 VirusTotal engines marked this domain as malicious when the evidence was captured. (External reputation `rule:EXT_BLACKLIST_HIGH`)

### 02 Page content
- The review of the page content rated it high risk. (Page content `rule:PAGE_RISK_HIGH`)
- The page shows few of the signs expected from a trustworthy operator. (Page content `rule:PAGE_TRUST_QUALITY_LOW`)
- The page content shows three or more warning signs that deceptive sites commonly use. (Page content `rule:PAGE_RED_FLAGS_STRONG`)
- The page runs on a free hosting-platform address instead of a domain of its own, a setup common to short-lived phishing and claim pages. (Page content `rule:PAGE_FREE_PLATFORM_ADDRESS`)
- The browser raised a warning while loading the page. (Page content `rule:PAGE_BROWSER_FLAGS_SUSPICIOUS`)
- The page has no description for search engines, which established sites usually provide. (Page content `rule:PAGE_SEO_MISSING_META`)
- The page carries none of the structured previews for search and social sharing that established sites usually provide. (Page content `rule:PAGE_SEO_NO_STRUCTURED`)

### 03 Several checks together
- Several independent checks pointed to risk at the same time. (Several checks together `rule:HYB_MULTIPLE_MODULES_HIGH_RISK`)

### 04 History in the web archive
- The web archive has almost no record of this domain, which fits a site that is new. (History in the web archive `rule:ARCH_PEN_YOUNG_AND_SPARSE`)

### 05 Registration and ownership
- As a site on pages.dev, this address has no registration record of its own (the platform's domain is registered, not the site). (Registration and ownership `rule:KF_WHOIS_INCOMPLETE`)

### 06 Behaviour in a sandbox
- A large share of the files the page loaded (scripts, images, fonts) came from other domains. This is about where its content is hosted, not about data being sent elsewhere. (Behaviour in a sandbox `rule:BEHAV_EXTERNAL_RATIO_MODERATE`)
- The page produced an unusually high number of errors while it ran. (Behaviour in a sandbox `rule:BEHAV_CONSOLE_ERRORS_HIGH`)
- The page exchanged network traffic with destinations TrustSniffer does not recognise. (Behaviour in a sandbox `rule:BEHAV_NONWHITELISTED_TRAFFIC`)
- The page sent data to a destination TrustSniffer does not recognise. (Behaviour in a sandbox `rule:BEHAV_NONWHITELISTED_POSTS`)
- The page made background requests to destinations TrustSniffer does not recognise. (Behaviour in a sandbox `rule:BEHAV_NONWHITELISTED_XHR`)
- An automated reading of the page's network activity judged some requests unusual for this kind of page. (Behaviour in a sandbox)
- The page made many background requests to other domains while it was open. (Behaviour in a sandbox `rule:BEHAV_EXTERNAL_XHR_HEAVY`)
- The page sent data to other domains many times while it was open. (Behaviour in a sandbox `rule:BEHAV_EXTERNAL_POSTS_HEAVY`)

### How related findings were counted

Some findings above describe the same underlying fact, and some are weak on their own. TrustSniffer counts each such group under one shared limit, so one fact is not counted several times and weak signals stay bounded.

- Third-party connections: 6 findings share one limit, because they all measure one fact: the page loads files from other hosts. The limit applied, so together they counted for less than their sum.
- Page quality: 2 findings share one limit, because each is weak evidence on its own. Together they stayed under the limit.
- Certificate and search-engine setup: 2 findings share one limit, because none of them is a sign of fraud on its own. Together they stayed under the limit.

## Identity verification


| Field | Value |
| --- | --- |
| Status | UNVERIFIED |

The operator behind the site could not be connected to a real-world brand or person. What the page shows, if anything, is listed below; none of it was independently checked.

- org:Fee Distribution
- on_site_identity

## What TrustSniffer observed

First-party facts recorded during the assessment of runc-12b.pages.dev.

- The request stayed on runc-12b.pages.dev. It was not redirected to another domain. (Clear)
- The earliest public archive of this site is from 2026-05-10. (Watch)
- It is hosted on CLOUDFLARENET, a network registered in US. (Noted)

## Domain intelligence


| Field | Value |
| --- | --- |
| Registrar | Not available |
| Hosting | CLOUDFLARENET - Cloudflare, Inc. |
| Network registered in | US |
| Server IP | 2606:4700:310c::ac42:2f5c (a CDN edge address; the server behind it was not observed) |
| Name servers | Not available |
| CDN / edge network | Detected (cloudflare) |
| Resolved IP addresses | 4 |
| Edge IP addresses | 4 |
| Likely origin IP addresses | 0 |
| SSL issuer | YE2 |
| SSL expiry | 2027-01-08 |
| First seen (web archive) | 187 days before capture; a site on pages.dev has no registration of its own |
| Domain expiry | Not available |
| Archive first seen | 2026-05-10 (187 days before capture) |
| Archive snapshots | 2 |
| Reputation | VirusTotal: 4 malicious, 1 suspicious \| AbuseIPDB (CDN edge address, not the host): 0% confidence, 0 reports \| Google Safe Browsing: 0 matches |

## About this assessment


**Was this report useful?** Tell other people what you think of TrustSniffer, good or bad. An honest review helps others decide whether to rely on these checks. [Review TrustSniffer on Trustpilot](https://www.trustpilot.com/review/trustsniffer.com)

A trust score summarises the evidence TrustSniffer could collect about runc-12b.pages.dev at a point in time: domain registration and age, hosting and certificate, the content the site served, and third-party reputation feeds. A high score means the signals were consistent with a legitimately operated site; a low or critical score means several risk patterns were present. It is a starting point for your own judgement, not a guarantee and not a legal finding. There is no human rating and no user review in it. A site can change after it is assessed.

## Related on TrustSniffer
- [Every website and wallet TrustSniffer has assessed](https://trustsniffer.com/directory), the full risk directory
- [Other websites assessed as low trust or critical risk](https://trustsniffer.com/directory/phishing-domains), phishing is among the evidence in this report
- [Check another website](https://trustsniffer.com/web-intelligence), run a new assessment
- [Check a crypto wallet address](https://trustsniffer.com/on-chain-risk), on-chain screening
- [The TrustSniffer Risk Index](https://trustsniffer.com/stats), how this verdict compares

## Guides
- [How to Report a Scam Website: Who to Tell and Why](https://trustsniffer.com/blog/how-to-report-a-scam-website)
- [Scam Website Statistics: Inside Our Data](https://trustsniffer.com/blog/scam-website-statistics-trustsniffer-data)
- [What Are Website Trust Signals?](https://trustsniffer.com/blog/website-trust-signals-explained)

---
*Source: [TrustSniffer](https://trustsniffer.com/report/runc-12b.pages.dev), independent automated trust & fraud analysis. Cite as https://trustsniffer.com/report/runc-12b.pages.dev · assessed 2026-11-13.*
