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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
Obfuscated document.write with encoded content
brand impersonation
The domain onlineksrtcswift.com impersonates the official Kerala State Road Transport Corporation (KSRTC). The real KSRTC online booking portal is ksrtcswift.com (a government domain), while this site uses a lookalike domain with 'online' prepended. The site extensively uses KSRTC branding, logos, official contact numbers, and government imagery to appear legitimate. (location: page.html:43, metadata.json:domain, page.html:7-11)
credential harvesting
The site presents a login/signup form that collects Indian mobile phone numbers and validates OTP via /api/resource/APIValidateAgentOTPLogin. Upon successful OTP validation, the site harvests full PII including customer name, age, email, gender, date of birth, date of anniversary, GST company name, and GST number — all sent in plaintext via GET request parameters to /my_profile/saveProfile. (location: page.html:96-279, page.html:619-697, page.html:832-840)
credential harvesting
Sensitive profile data (name, age, email, gender, GST number, mobile, DOB, DOA) is transmitted via HTTP GET request with all PII as URL query parameters, making them visible in server logs, browser history, and any intermediary proxies. The endpoint is /my_profile/saveProfile. (location: page.html:834)
phishing
The site is a convincing phishing replica of KSRTC SWIFT's official bus ticketing platform. It includes real KSRTC contact numbers (0471-2463799, 9447071021, 18005994011), official social media links, realistic route and destination content, and app store links — all designed to deceive users into believing they are on the legitimate government booking portal. (location: page.html:913-914, page.html:963-983, page.html:2019-2023)
hidden content
The login/signup modal (div.signup-wrap) is rendered with display:none and is hidden from users on page load, but contains fully functional credential collection forms including OTP generation, OTP validation, and profile data collection. The complete profile form is also hidden (style='display:none') and revealed only after OTP validation. (location: page.html:93-287, page.html:317-330, page.html:103-109)
hidden content
Commented-out HTML includes a footer discount banner referencing Paytm cashback promotions with terms dated October 2018, suggesting this template was originally built for a different operator or was copied/repurposed. The commented code references /img/paytm-new.jpg and Paytm-specific cashback T&Cs. (location: page.html:3767-3790, page-hidden.txt:161-234)
social engineering
The site uses social proof tactics including fabricated or unverifiable customer testimonials (Shaji Thekkekara, Mukesh Kumar, Krishna Kumar) with generic 'Traveller' designations, loyalty benefit messaging ('earn loyalty benefits'), and urgency messaging ('Book round trip tickets - Get 10% Discount') to manipulate users into submitting personal data and completing transactions. (location: page.html:1899-1950, page.html:97-98, page.html:1357-1358)
curl https://api.brin.sh/domain/onlineksrtcswift.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
onlineksrtcswift.com 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.