context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
All script tags throughout the page use a non-standard MIME type 'a1fa5168d329f5a9acca56b0-text/javascript' instead of 'text/javascript'. This is a Cloudflare Rocket Loader obfuscation technique where scripts are deferred by changing their type attribute. While used by Cloudflare legitimately, the token 'a1fa5168d329f5a9acca56b0' appears as a consistent identifier across all scripts including third-party analytics, Facebook Pixel, Alexa certify, and Google Tag Manager, masking which scripts are actually executing on page load and making static analysis of active scripts difficult. (location: page.html:47-118, 1668-1903 — all <script> tags use type='a1fa5168d329f5a9acca56b0-text/javascript')
social engineering
OMICS International/omicsonline.org is a well-documented predatory publisher listed on multiple watchdog databases (formerly on Beall's List). The site uses social proof tactics including fabricated or inflated statistics ('700+ peer-reviewed journals', '50,000+ Editorial Board Members', '15 million readers', '3000+ scholarly conferences per year') and curated testimonials from named academics to build false credibility. The FTC sued OMICS Group in 2016 for deceptive practices including misrepresenting journal indexing and hiding article processing charges. This constitutes ongoing social engineering targeting researchers. (location: page.html:286, 418-420 — banner and About Us section; page.html:1404-1450 — testimonials section)
social engineering
The site collects manuscript submissions and researcher registration data under the guise of a legitimate academic publisher. Researchers are directed to 'Submit Manuscript' and 'Register' pages, where they may be solicited for article processing charges (APCs) under false pretenses of peer review and indexing. The 'Article Processing Charges' button is prominently featured. This is a known predatory publishing tactic to extract payment from academics. (location: page.html:750-752 — Article Processing Charges, Journal Impact Factor, Peer Review Process buttons; page.html:152 — Register link)
hidden content
A large commented-out block of HTML in the footer contains a fully functional contact form with multiple email addresses (agriaquaculture@omicsonline.com, business@omicsonline.com, clinicaljournals@omicsonline.com, etc.) and phone extension fields with empty labels. These hidden contact blocks have no visible display names, potentially used for harvesting contact or tracking purposes without user awareness. (location: page.html:1463-1623 — commented-out footer contact grid; page-hidden.txt:411-571)
hidden content
A commented-out floating bell icon widget linking to 'https://www.globaltechsummit.com' with an image loaded from 'https://www.vizagtechsummit.com/images/bellicon.png' is present. These are third-party domains embedded in a fixed-position overlay element that was apparently active at some point and then hidden via HTML comment. The cross-domain image load from vizagtechsummit.com represents a covert third-party tracking or redirect vector that is not disclosed to users. (location: page.html:1906-1921; page-hidden.txt:584-599)
malicious redirect
The 'Scholars Central' link in the New Initiatives section uses HTTP (not HTTPS): 'http://www.scholarscentral.org/'. Additionally, numerous journal submission option values throughout the page link to scholarscentral.org via HTTP, exposing users to potential downgrade or man-in-the-middle attacks when following these links. (location: page.html:1377 — http://www.scholarscentral.org/; multiple <option> values in the hidden journal selector form)
curl https://api.brin.sh/domain/omicsonline.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
omicsonline.org currently scores 49/100 with a suspicious verdict and medium 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.