context safety score
A score of 35/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
cloaking
Page loads content in transparent or zero-size iframe overlay
prompt injection
Hidden HTML element contains AI-targeting instructions
social engineering
Wave Browser has a documented history as a potentially unwanted program (PUP) that installs bundled software and hijacks browser settings. The site uses environmental/charitable messaging ('Save the Ocean', '4ocean partnership') as a trust-building cover to encourage downloading a browser that has been flagged by security researchers and antivirus vendors for aggressive installation and persistence behaviors. This cause-washing technique is a classic social engineering pattern designed to lower user defenses. (location: page-text.txt:1 - hero section and throughout visible content)
social engineering
The page discloses that searches are 'powered by Yahoo by default' — a hallmark of browser hijacking monetization. The framing minimizes this as a user-friendly default while burying the revenue model (search engine partnership commissions). This is deceptive presentation designed to obscure the true commercial nature of the product. (location: page-text.txt:1 - 'Searches are powered by Yahoo by default')
hidden content
The page embeds an audio element positioned off-screen using CSS: 'audio{left:-999999px;opacity:0;pointer-events:none;position:fixed;top:-999999px}'. Audio files (yad_dl_top_right.mp3, yad_edge.mp3, yad_firefox.mp3) are prefetched. The filenames suggest these are triggered during competing browser detection flows. This is hidden/non-visible content serving undisclosed behavioral purposes. (location: page.html:13 (inline style), page.html:94-96 (prefetch links))
hidden content
The page body contains a large number of A/B test flags embedded as CSS body classes: '--v2110_on --organic_maybe --bigStub_on --t2-92_on --vuentp_on --wavwbnui_on --fourTiles_on --richSuggestions_on --sponsoredGroup_on --darkmode_on --nadm_on --newTblaTag_on --apiWaveBrowNetNTP_on --CapOneLimit_on --waveNews_on --freePro_on --4ocean_on --sidebarItemRemoval_on --fifthql_on --maxSesMatchesOverride_on --taboolaBlacklistAdsCheck_on'. Flags like 'taboolaBlacklistAdsCheck_on', 'sponsoredGroup_on', 'nadm_on', and 'CapOneLimit_on' indicate hidden ad-targeting and monetization logic not disclosed to the user. (location: page.html:157 - body class attribute)
hidden content
The page exposes internal API endpoints in a publicly visible JavaScript config block: waveNewTabApi points to 'https://mywavehome.net' (a separate domain), waveCoreApi to 'https://api.wavebrowser.net', and downloadApi to 'https://download.wavebrowser.co'. The new-tab API domain 'mywavehome.net' is a separate undisclosed domain that would silently control the user's new tab page after install. (location: page.html:158 / page-text.txt:2 - window.__NUXT__.config)
malicious redirect
The download infrastructure routes through 'download.wavebrowser.co' (a subdomain), and the new tab page is silently controlled by 'mywavehome.net' — a separate domain not prominently disclosed on the marketing page. Post-install, users' new tab sessions would be redirected to this undisclosed domain, enabling search hijacking and monetization without clear user consent. (location: page-text.txt:2 - window.__NUXT__.config downloadApi and waveNewTabApi values)
social engineering
The page includes prefetched audio files named 'yad_edge.mp3' and 'yad_firefox.mp3', suggesting targeted behavioral flows that activate when users are detected as running Edge or Firefox. This implies the site serves different persuasion content based on detected browser, a form of targeted social engineering to encourage switching away from competitor browsers. (location: page.html:95-96 - prefetch audio links)
curl https://api.brin.sh/domain/wavebrowser.coCommon questions teams ask before deciding whether to use this domain in agent workflows.
wavebrowser.co currently scores 35/100 with a suspicious verdict and low confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this domain.
Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.
brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.
Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.
brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.
No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.
Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.
Learn more in threat detection docs, how scoring works, and the API overview.
Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.