Is masterfap.net safe?

suspiciouslow confidence
23/100

context safety score

A score of 23/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.

identity
50
behavior
50
content
0
graph
30

11 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

high

obfuscated code

Heavily obfuscated JavaScript using URL-encoded character shifting/Caesar-cipher rotation with large lookup tables. The script dynamically constructs strings and URLs at runtime to evade static analysis, and loads a third-party script from janitorprecisiontrio.com with onerror/onload callbacks wired to an internal function (uqtyfnn). This pattern is characteristic of malvertising loaders and ad-fraud scripts. (location: page.html:81-82)

high

malicious redirect

Third-party script loaded from 'janitorprecisiontrio.com' (data-clocid='2018465') — a domain with no legitimate reputation context. Combined with the obfuscated loader on line 81, this script is dynamically invoked and can trigger pop-unders, forced redirects, or drive-by downloads. The domain name is a classic nonsense-compound pattern used by ad-fraud/malvertising networks. (location: page.html:82)

medium

malicious redirect

Link to 'http://dpnode.top/?channel=masterfap' uses plain HTTP (not HTTPS), an unrecognized domain, and a tracking/channel parameter. This is a classic affiliate redirect chain pattern that may lead to scam or malware landing pages. (location: page.html:356)

medium

malicious redirect

Link to 'https://s.gentlefieldpattern.com/v1/d.php?z=2134' and 'https://s.gentlefieldpattern.com/v1/d.php?z=3076' are opaque redirect/tracker URLs on an unrecognized domain using a PHP redirect script with numeric zone parameters. This pattern is used by ad-fraud and malvertising networks to route traffic to unpredictable destinations. (location: page.html:164,171)

medium

malicious redirect

Link to 'https://engine.forbiddenhunter.com/?695739137' is a hidden anchor element (no visible text, no dimensions described) pointing to an unknown domain with a numeric query parameter — consistent with a hidden pop-under or background redirect trigger used in malvertising. (location: page.html:691)

medium

social engineering

Multiple affiliate sidebar links use sexually explicit and degrading anchor text (e.g., 'Undress AI slut', 'Ai Jerk OFF', 'Undress her', 'Free Undress Maker') to manipulate users into clicking through to third-party AI image-generation services. These services harvest user engagement and may solicit account creation or payment credentials. (location: page.html:149-180)

medium

social engineering

The 'Onlyfans Accounts' header button links to 'https://linkinbio.fun/mstrfpnov' — an opaque link-in-bio redirect that obscures the true destination. The label implies free access to OnlyFans accounts, which is a common lure used to drive traffic to scam, phishing, or subscription-harvesting sites. (location: page.html:318)

medium

brand impersonation

The site self-describes as 'Best OnlyFans Leaks Website' and prominently uses OnlyFans branding, terminology, and creator names to attract traffic. It impersonates or exploits the OnlyFans brand to distribute allegedly leaked private content, misleading users about the legitimacy and authorization of the content. (location: page.html:10,15-16,349-350)

medium

hidden content

An anchor element with id='myBtn2' has no visible text or label and is styled as a fixed-position overlay button using a background image. It links to 'https://engine.forbiddenhunter.com/?695739137' — effectively a hidden clickable element that could intercept user clicks or serve as a pop-under trigger invisible to the user. (location: page.html:691)

low

social engineering

The site uses a fake OneTrust-styled age-verification overlay (reusing '.onetrust-pc-dark-filter' CSS class name from the legitimate OneTrust consent SDK) to create a false sense of compliance and legitimacy, while only setting a simple cookie. This mimics a real GDPR/consent tool to lower user suspicion. (location: page.html:647-684)

API

curl https://api.brin.sh/domain/masterfap.net

FAQ: how to interpret this assessment

Common questions teams ask before deciding whether to use this domain in agent workflows.

Is masterfap.net safe for AI agents to use?

masterfap.net currently scores 23/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.

How should I interpret the score and verdict?

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.

How does brin compute this domain score?

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.

What do identity, behavior, content, and graph mean for this domain?

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.

Why does brin scan packages, repos, skills, MCP servers, pages, and commits?

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.

Can I rely on a safe verdict as a full security guarantee?

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.

When should I re-check before using an entity?

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.

Last Scanned

March 4, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Disclaimer

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.

start scoring agent dependencies.

integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.