context safety score
A score of 43/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
js obfuscation
JavaScript uses Function constructor for runtime code generation
social engineering
The site prominently promotes a paid VIP membership zone (ZONA VIP, ACCESO VIPS, HACERSE VIP) with multiple calls-to-action and banner images targeting users of an adult content site. The membership login page (membership-login/) and join page (membership-join/) collect user credentials and payment information under the pretext of exclusive adult content access, a classic premium-lure social engineering pattern. (location: page.html:234-235, page.html:267-268, page.html:2099-2100)
credential harvesting
The site operates a membership/login system (Simple Membership plugin v4.7.2 at /membership-login/ and /membership-join/) collecting usernames and passwords on an adult content platform. The login page is linked from multiple high-visibility banner images. The WordPress AJAX endpoint (admin-ajax.php) is exposed and used for authentication flows. (location: page.html:97, page.html:118, page.html:234, page.html:267)
malicious redirect
PopCash ad network script is injected directly into the page body via dynamically created script tags loading from cdn.popcash.net (with cdn2.popcash.net as fallback). PopCash is a well-known pop-under/redirect ad network that triggers unsolicited browser redirects and pop-unders to potentially malicious or scam destinations when users interact with or simply visit the page. (location: page.html:2288-2289, page-text.txt:1870-1871)
hidden content
Two Elementor HTML widget elements render single white-colored period characters ('<p><span style="color: #ffffff;">.</span></p>') that are invisible against a white background. While likely used as layout spacers, this pattern matches hidden content injection used to embed invisible text or markup. (location: page.html:828, page.html:1220)
social engineering
A 'Favoritos y Top del Mes' widget contains a 'Ver Ahora' (Watch Now) button for 'Mi Mama Latina Culona' that incorrectly links to a different post URL (/sexo-con-mama-27-minutos-video-porno/) rather than the post it is associated with (/mi-mama-latina-culona-parte-2-video-porno-en-espanol/). This link mismatch could be used to redirect users to unexpected content or track deceptive click patterns. (location: page.html:1326)
social engineering
Cookie consent bar links to 'http://comicsporno.es/politica-de-cookies/' (a different domain, using HTTP not HTTPS) for the privacy/cookies policy. This cross-domain HTTP link in a consent notice could expose users to tracking or manipulation on a separate unrelated domain, and may be used to legitimize data collection under a misleading consent framework. (location: page.html:2139)
curl https://api.brin.sh/domain/melapelocondibujos.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
melapelocondibujos.com currently scores 43/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.