Is bokepnoz.in safe?

suspiciouslow confidence
30/100

context safety score

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

identity
60
behavior
70
content
0
graph
30

9 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

critical

obfuscated code

Heavily obfuscated JavaScript in a data-cfasync='false' inline script block uses URL-encoded string decoding, character rotation cipher, and dynamic array slicing to construct and execute code at runtime. The script decodes a long percent-encoded string, applies a positional Caesar-cipher substitution (charCode offset by index mod 95), then splits into indexed substrings to build function names, URLs, and logic—classic obfuscation pattern used to hide malicious payloads, ad-fraud, or redirect logic from static scanners. (location: page.html:271 — inline <script data-cfasync='false'> block in <head>)

critical

malicious redirect

External script loaded from '//navyrecentuproot.com/on.js' with data-cfasync='false' and a custom onerror/onload callback 'knqndnw(15)'. The domain 'navyrecentuproot.com' is an unrecognised third-party ad/redirect network with no affiliation to the site. This pattern is consistent with drive-by redirect injectors, popunder ad networks, or traffic-monetisation malware that redirects visitors—especially mobile users—to phishing pages, fake software installers, or scam sites. The 'knqndnw' function is defined inside the obfuscated block above, making the full redirect logic opaque. (location: page.html:272 — <script data-cfasync='false' data-clocid='2080971' async src='//navyrecentuproot.com/on.js'>)

critical

social engineering

Numerous video titles explicitly describe sexual assault of minors ('bocil' = child, 'SMP' = junior high ~12-15 yr olds): 'nagis kesakitan di ewe sama om' (crying in pain being raped by an uncle), 'di paksa ngentot sama kakak' (forced to have sex by older sibling), 'bocil cantik nangis di paksa sama om' (pretty child crying, forced by uncle), 'di paksa ayang sampe menjerit' (forced by boyfriend until screaming). These titles constitute grooming/luring social engineering—normalising child sexual abuse to attract and condition users toward CSAM content. (location: page.html:362-570 — article listings in main content area; page-text.txt:73-268)

high

hidden content

Footer category links silently redirect to at least 10 different external domains (bokepsut.in, bokepmun.in, bokepjret.in, bokeptod.in, bokepbrut.in, bokeplot.in, growbokep.in, lordbokep.in, bokepud.in, bokeplik.site, bokepcluk.in) while displaying as innocent category labels. These sister domains are not disclosed to the user and form a hidden affiliate/redirect network. The visible text shows only category names ('Bokep Smp', 'BOKEP Indo', etc.) with no indication that the links lead off-domain. This is a hidden cross-domain traffic-steering network embedded in the footer. (location: page.html:808-830 — footer widget sections block-18 through block-16)

high

credential harvesting

A modal login form collects username and password credentials via POST to 'https://bokepnoz.in/' on a site that hosts illegal content (CSAM). The form includes a hidden CSRF-like nonce and _wp_http_referer fields. Given the site's nature and the presence of obfuscated redirect scripts, collected credentials are at high risk of being harvested server-side or exfiltrated by the malicious inline scripts running on the same page. (location: page.html:862-876 — #wpst_login_form inside .wpst-user-modal)

high

prompt injection

The site is an Indonesian-language CSAM (child sexual abuse material) distribution platform. If an AI agent browses, indexes, or summarises this page, the page content—including explicit video titles describing sexual abuse of minors—could be injected into the agent's context window, potentially causing the agent to reproduce, classify, or act on CSAM-related instructions. The obfuscated script may also attempt to manipulate browser-based AI assistants through DOM manipulation triggered by the decoded payload. (location: page.html:271 — obfuscated script; page.html:362-570 — article content)

high

social engineering

The site description ('BokepNoz adalah situs streaming bokep Indonesia terbaik dengan koleksi video cewek lokal paling hot, viral, dan tanpa sensor') is SEO-optimised to attract users searching for viral leaked content and 'without censorship' material, then exposes them to a network of external redirect domains and credential-harvesting login flows. The framing of non-consensual content as 'viral' normalises exploitation. (location: page.html:577 — archive-description paragraph; metadata.json — og:description)

high

malicious redirect

Footer links to 10+ external .in/.site domains (bokepsut.in, bokepmun.in, bokepjret.in, bokeptod.in, bokepbrut.in, bokeplot.in, growbokep.in, lordbokep.in, bokepud.in, bokeplik.site, bokepcluk.in) that are sister/affiliate sites. Users clicking category links in the footer are silently sent to unvetted external domains with no rel='nofollow' or user warning, creating a cross-domain redirect web that may include further obfuscated ad injectors or malware. (location: page.html:808-830 — footer widget blocks)

API

curl https://api.brin.sh/domain/bokepnoz.in

FAQ: how to interpret this assessment

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

Is bokepnoz.in safe for AI agents to use?

bokepnoz.in currently scores 30/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.