context safety score
A score of 33/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
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
malicious redirect
All post content links redirect users from showpm.in to a separate domain showpm.world (e.g., https://www.showpm.world/p/pavitrem-04032026-episode.html). Every single post body contains only a large 'PLEASE OPEN' link pointing to this external domain, indicating a systematic traffic-redirect scheme designed to funnel visitors to an uncontrolled third-party site. (location: page.html: post-body elements, lines 456, 500, 544, 588, 632, 676, 720, 764, 808, 852, 896, 940, 1160)
hidden content
Multiple CSS rules explicitly hide significant portions of the page content from users: .post-body {display:none;}, .post-footer {display:none;}, .comment-link {display:none;}, .post img {display:none;}, .post blockquote {display:none;}, h2.date-header {display:none;}, .post-labels {display:none;}, .post-rating {display:none;}. Post bodies and footers are set to display:none, meaning content visible in the HTML (including redirect links) is hidden from casual viewing but present in the DOM for scraping or automated agent consumption. (location: page.html: <style> block lines 40-48)
social engineering
The site uses oversized, bold 'PLEASE OPEN' call-to-action links styled with 'font-family: Anton; font-size: xxx-large' and a pointing finger emoji (👉) to aggressively pressure users into clicking redirect links to showpm.world. This is a high-pressure CTA pattern designed to manipulate user behavior. (location: page.html: all post-body sections, e.g. lines 456, 500, 544)
brand impersonation
The site impersonates or heavily references legitimate Malayalam TV broadcast brands including Asianet, Zee Keralam, Surya TV, and Mazhavil Manorama in its title, navigation, and post content. The page title keyword-stuffs with numerous competitor/official domain names (ddmalar.com, kuthira.com, kurumbi.com, thiramala.com, kaduvatv.com, mallupm.com, go5pm.com) to appear as an official or affiliated streaming source for copyrighted content. (location: page.html: <title> tags lines 5-7, navigation links lines 424-428)
hidden content
The page title contains two separate <title> tags with extensive SEO keyword stuffing listing numerous competitor domains and brand names. The second title tag (line 7) is redundant and appears designed to manipulate search engine indexing rather than provide user-facing information. (location: page.html: lines 5-7)
social engineering
Post entries show date mismatches between the URL path (e.g., /2026/02/ suggesting February 2026) and the displayed title text claiming 'March 2026 Episode'. This date manipulation is used to make old or recycled content appear as current daily episodes, deceiving users about content freshness. (location: page.html: post titles at lines 978, 1022, 1066, 1110 (February URLs but March dates in titles))
curl https://api.brin.sh/domain/showpm.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
showpm.in currently scores 33/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.