context safety score
A score of 43/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 checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
Heavy JavaScript obfuscation using a rotating-array self-executing function with hex-encoded offsets (e.g., parseInt(Xo(0xac)), Xe(0x94), etc.) and a custom string-decoding function R(K,h)/X(). The obfuscated block assembles strings for 'adManager', 'proxy', 'secret', 'static' and similar terms at runtime, concealing its true purpose from static analysis. This pattern is a well-known malvertising/payload-delivery obfuscation technique. (location: page.html:979 and page-text.txt:764 (inline <script data-cfasync='false'> block))
malicious redirect
Two third-party ad/tracker scripts loaded from suspicious domains with randomised path components: '//earringsatisfiedsplice.com/bultykh/ipp24/7/bazinga/1986889' and '//diagramjawlineunhappy.com/t/9/fret/meow4/1974032/746ec7ae.js'. Both domains use nonsense-word combinations typical of malvertising networks, load asynchronously with data-cfasync='false' to bypass Cloudflare checks, and are consistent with known adware/redirect-chain infrastructure. (location: page.html:975 and page.html:977)
malicious redirect
JavaScript popup logic dynamically constructs and injects a full-screen overlay linking to 'https://undress.love/' — an AI-undressing/non-consensual imagery service. The popup fires on page load for both mobile and desktop visitors via cookie-gated logic, and the injected anchor uses target='_blank' with rel='nofollow' to open the destination in a new tab, functioning as a forced redirect/ad. (location: page.html:1103-1127 (and duplicated at page-text.txt:888-912))
brand impersonation
The site's title, meta description, navigation labels ('OnlyFans Videos', 'OnlyFans Leak tool', group named 'OnlyFans Leaks'), and page branding directly appropriate the OnlyFans trademark to attract users searching for OnlyFans content. The site is not affiliated with OnlyFans and distributes content claimed to be leaked from OnlyFans, Patreon, and other platforms, constituting trademark-based brand impersonation to drive traffic. (location: page.html:6-7 (title/meta), page.html:233-286 (sidebar nav), page.html:741 (group label 'OnlyFans Leaks'))
social engineering
All interaction actions (Like, Follow, Post comment) are wired to '/signup/' via onclick handlers and href attributes, compelling users to create an account. The textarea placeholder reads 'You must be logged in to post a comment. Please, tap here for registration.' — a deliberate dark-pattern that channels all engagement into credential/account harvesting via registration. (location: page.html:433,439,451-455 and repeated throughout all post cards)
credential harvesting
The 'Onlyfans Leak tool' link (/request/) and the site-wide 'Follow Free' / 'Log In' / '+ Create post' CTAs funnel users toward account creation and login pages. All interactive elements (like, follow, comment) redirect to /signup/, creating a systematic funnel designed to harvest user credentials and personal data under the pretext of accessing leaked adult content. (location: page.html:283-286 (/request/ link), page.html:182 (create post), page.html:192-195 (Log In nav item), page.html:439,490,541 (Follow Free buttons))
hidden content
A zero-dimension tracking pixel is embedded at the bottom of the page body: <img width='0' height='0' src='https://whos.amung.us/widget/1ku4kdvpoc.png' alt='amung'/>. This invisibly pings a third-party analytics/tracking service on every page load without any user notice or consent disclosure. (location: page.html:974)
social engineering
The site meta description falsely frames stolen/leaked private content as a 'social network' with 'high quality and free' content from 'OnlyFans, Patreon and other nude content platforms', framing non-consensual intimate image distribution as a legitimate social platform to lower user suspicion and encourage registration and engagement. (location: page.html:7 (meta description))
curl https://api.brin.sh/domain/thefap.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
thefap.net currently scores 43/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.