context safety score
A score of 26/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
phishing
1 deceptive links where visible host does not match destination host
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 eval() with String.fromCharCode — common obfuscation
js obfuscation
JavaScript uses eval(atob()) — base64-encoded payload execution
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The site uses the term 'Sarkari' (meaning 'Government' in Hindi) and 'VLE' (Village Level Entrepreneur, an official Government of India designation under CSC scheme) in its domain name and branding to create the impression of an official government portal. The meta description states 'Welcome To Official Sarkari VLE Portal' and the site claims to be a trusted platform for 'official' government services. The footer disclaimer itself acknowledges this risk, stating 'not affiliated with the official CSC (common service centres) OR VLE (Village Level Entrepreneur) of the Government of India', confirming the branding deliberately mimics official government identity. (location: page.html:9,12,18,20 — title, meta description, og:title, og:site_name; page.html:2210 — footer disclaimer)
social engineering
The site repeatedly uses authority-signaling language to establish false legitimacy: 'Official Sarkari VLE Portal', 'trusted platform', 'reliable government-related information', 'official financial assistance updates'. It positions itself as a one-stop guide for sensitive government services including Aadhaar Card, PAN Card, PM Kisan, NREGA, e-Shram Card, Ayushman Card, and Voter Card — all services that involve personal identity documents and financial data. This creates false trust with vulnerable users seeking government assistance. (location: page.html:858,2179 — welcome text and about section; page-text.txt:124,1382-1383)
social engineering
The site includes content about 'Sarkari Loan Schemes', 'government-backed financial support', and 'bank loan information' alongside step-by-step guides for accessing government financial schemes. Combining loan/financial assistance content with impersonated government branding creates conditions for financial social engineering targeting users seeking subsidies and loans. (location: page.html:2177-2179 — heading and body text describing loan scheme guidance; page-text.txt:1381-1383)
obfuscated code
The LaraPush push notification integration loads a remote script from cdn.larapush.com and executes a base64-encoded configuration string via eval(). The decoded config reveals a Firebase project ('sarkari-job-show-push'), an API token endpoint at a third-party domain (hpush.neareshop.com), and a Firebase API key embedded in the page. Using eval() with atob()-decoded payloads is an obfuscation pattern that hides the full behavior from static analysis and enables the site to push notifications to subscribed users from an external service not controlled by users. (location: page.html:106-110 — LaraPush script block with eval(additionalJsCode))
hidden content
A post titled 'test1' linking to sarkarivle.com/test/ (post ID 2635) appears across all content listing sections (Latest Update, Admit Card, Result, New Job, New job). This placeholder/test post is present in production and appears in multiple categorized content widgets, suggesting either incomplete content management or a content slot that could be repurposed for injected links without obvious visibility to users. (location: page.html:1205,1335,1478,1907,2050 — test1 entry repeated across all TPG grid widgets)
curl https://api.brin.sh/domain/sarkarivle.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
sarkarivle.com currently scores 26/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.