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
malicious redirect
The page is served at rupalipalace.co.uk (a UK restaurant domain) but all canonical URLs, assets, links, and branding point to legoutrmets.com — a Vietnamese adult content site. The canonical tag explicitly redirects crawlers and agents to https://legoutrmets.com/. This is a domain hijack/cloaking arrangement where a legitimate-seeming UK domain silently delivers a completely different site's content. (location: page.html:11 — <link rel="canonical" href="https://legoutrmets.com/">)
obfuscated code
A large obfuscated JavaScript block labeled '<!--PUPUNDER-->' uses decodeURI on a heavily encoded string, applies a Caesar-cipher-style character rotation (charCode offset by position mod 95), then reconstructs and executes a popunder/redirect payload at runtime. The decoded logic drives forced popup/redirect behaviour to gambling and adult sites. The obfuscation is specifically designed to evade static analysis. (location: page.html:36 — <script data-cfasync="false">!function(){"use strict";for(var n=decodeURI("wd%60andp%5E...)
malicious redirect
JavaScript popup configuration opens random URLs from ['https://jun8899.me/sextop2', 'https://mb6688.me/sextop2MB66'] in new tabs on user click, with a 10-second initial delay and 60-second interval. These are affiliate/gambling redirect links triggered covertly on any page interaction, without user consent or disclosure. (location: page.html:44-92 — popupConfig links array and handleClick/openPopup functions)
malicious redirect
An external script is loaded from //bodybossmotivate.com/on.js with callbacks to jdzby() — a function defined within the obfuscated PUPUNDER block. This third-party script is part of the popunder ad network infrastructure and executes arbitrary external code on page load. (location: page.html:37 — <script data-cfasync="false" data-clocid="2030212" async src="//bodybossmotivate.com/on.js">)
hidden content
A third-party ad script from waust.at (a known adware/traffic monetisation network) is loaded silently: _wau.push(['classic','7y0cufjq58','xis']). This tracker/ad injector runs invisibly with no user-visible disclosure and is associated with popunder and redirect ad networks. (location: page.html:24 — <script id="_wauxis">var _wau = _wau || []; _wau.push([...]))
hidden content
A conditional script dynamically appends an external ad script from vipads.live (vn/FD2635C2-E5F4-1993-33-E9455AE179BE.blpha) only when window.innerWidth < 500 (mobile devices). This targeted payload injection is hidden from desktop analysis and serves a different ad/redirect payload specifically to mobile users. (location: page.html:132-138 — conditional script injecting vipads.live source on mobile)
hidden content
A commented-out script tag references https://www.vipads.live/vn/A4FA082A-2351-1993-33-DBDDC45340F3.blpha under a 'CATFIT BANNER' comment. While commented out in HTML, the mobile-targeted block above loads a different vipads.live GUID, suggesting rotation of ad payloads. The .blpha extension is non-standard and indicative of obfuscated ad payload delivery. (location: page.html:39-41 — <!-- CATFIT BANNER commented block referencing vipads.live -->)
social engineering
The page targets searches including 'Hoc Sinh Bi Lua' (students being deceived/tricked), 'Gai Non' (underage girls), 'hiep em' (assault/rape), and 'em gai moi lon long con chua moc' (very young girls). These search terms suggest the site is used to attract users seeking content involving minors or non-consensual scenarios, which constitutes exploitation-based social engineering and potential CSAM facilitation. (location: page.html:623-643 — recent search terms section)
brand impersonation
The domain rupalipalace.co.uk is an established UK business (domain age 14,833 days, ~40 years) being used to serve content for legoutrmets.com. The page HTML, metadata, canonical links, and all branding are entirely from legoutrmets.com. The legitimate rupalipalace.co.uk brand is being exploited to lend credibility or hosting cover to the adult/gambling content operation. (location: metadata.json + page.html:11-20 — domain mismatch between rupalipalace.co.uk and all canonical/OG references to legoutrmets.com)
hidden content
Cookie-based click tracking silently counts body clicks (setCookie 'bodyClicked') and ad suppression timestamps ('adsHiddenUntil') to control ad visibility and evade detection. After 4 clicks ads are suppressed, which can also be used to hide malicious content from automated scanners that simulate clicks. (location: page.html:142-198 — setCookie/getCookie click tracking and handleAdVisibility logic)
curl https://api.brin.sh/domain/rupalipalace.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
rupalipalace.co.uk 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.