context safety score
A score of 34/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
brand impersonation
Site impersonates the well-known 'Soap2Day' piracy streaming brand, using its name, logo, and branding extensively. The page title explicitly references 'Soap2day.com' and 'Soap2day2' to capture search traffic for the original brand. Multiple alternate domain aliases (soap2day.day, ww25.soap2day.day, uk.soap2day.day, au.soap2day.day, 123movies.soap2day.day) suggest a coordinated brand-squatting network distributing pirated content under the Soap2Day name. (location: page.html:17, page.html:304, page.html:318)
malicious redirect
Third-party ad script loaded from 'bvtpk.com' via obfuscated inline JavaScript that dynamically creates and appends a script element. This pattern is commonly used by malvertising networks to inject redirects or pop-unders without direct attribution in the HTML source. (location: page.html:98)
malicious redirect
Ad network script loaded from 'quietleafgarden.com' — an unrecognized third-party domain injecting JavaScript (invoke.js and a hash-named .js file). These scripts run in full page context and can perform drive-by redirects, pop-ups, or malicious payload delivery. Two separate scripts from this domain are present. (location: page.html:431, page.html:700)
malicious redirect
Ad/tracker script loaded from 'yw.noritesfarrago.com' via an async script tag embedded mid-content. This is an unrecognized third-party ad network domain with a randomly-generated-looking subdomain, consistent with malvertising infrastructure used for redirects or ad fraud. (location: page.html:324)
hidden content
Yandex Metrica tracking pixel loaded via a noscript tag with inline image positioned off-screen at 'position:absolute; left:-9999px'. This off-screen pixel is invisible to users and used for covert behavioral tracking and fingerprinting of visitors without consent disclosure. (location: page.html:659)
social engineering
Page contains deliberate social engineering text designed to build false trust: claims the site has been 'verified by Eset, VirusTotal, McAfee, Avast, Norton, F-Secure', pre-emptively addresses user skepticism ('You might think these guys seem suspicious'), and promotes sideloading an Android APK from unknown sources ('you'll need to allow installation from unknown sources'). This is a classic technique to lower user security defenses. (location: page-text.txt:270-272, page.html:369-373)
social engineering
App section encourages users to download an Android APK ('Soap 2day 2026 official apk') that requires enabling installation from unknown sources — bypassing Android's built-in security controls. This is a known vector for distributing malware-laced APKs under the guise of a trusted brand. (location: page.html:367-369, page-text.txt:267-269)
obfuscated code
The bvtpk.com script injection uses a self-invoking obfuscated pattern: '(function(s){s.dataset.zone=...,s.src=...})([document.documentElement, document.body].filter(Boolean).pop().appendChild(...))' — deliberately obscuring the script injection to evade static analysis. This is a recognized obfuscation technique used by malvertising networks. (location: page.html:98)
hidden content
Footer contains keyword-stuffed tag links ('soap2day', 'soap 2day', 'soaptoday', 'soap today', 'soap2day is', 'soup2day') all pointing to the root URL. These are SEO manipulation anchors designed to influence search engine rankings and direct search traffic from competing/variant brand spellings to this site. (location: page.html:537-542)
brand impersonation
Page title and meta description reference multiple competing brand names ('Soaptoday', 'Soap 2 Day', 'Soap2say', 'HDtoday', 'Soaper TV', '123Movies') to harvest search traffic from users looking for those separate brands, constituting multi-brand impersonation for SEO manipulation. (location: page.html:17, page.html:20)
curl https://api.brin.sh/domain/soap2day.dayCommon questions teams ask before deciding whether to use this domain in agent workflows.
soap2day.day currently scores 34/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.