Is tamilprint55.art safe?

suspiciouslow confidence
38/100

context safety score

A score of 38/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.

identity
100
behavior
15
content
20
graph
30

6 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

high

obfuscated code

Inline script uses Base64-encoded URLs stored in array 'c' and dynamically decodes them with atob() at runtime to load external scripts (popunder/ad network scripts from intellipopup.com, cloudfront.net, cjkpdzlgm.com, yzuflrxgejd.com). The script also uses a time-based kill switch (1797431563000) and fingerprints the window object to avoid double-execution. This pattern is characteristic of malvertising injection loaders. (location: page.html:188 / page-text.txt:104)

high

malicious redirect

The obfuscated script loads a popunder ad network (intellipopup.com) and associated floating ad scripts. Popunder networks on piracy sites are routinely used to redirect users to malware distribution pages, tech-support scams, and credential-harvesting sites. The script is configured with 'topmostLayer: auto' and 'popundersPerIP: 0' (unlimited), maximizing redirect exposure per visitor. (location: page.html:188)

medium

hidden content

A span with style 'color: white;' on a white background renders SEO keyword stuffing invisible to users: 'tamilprint,tamilprint1.com movies tamilprint1.live 2021 Movies download'. This is used to manipulate search rankings and lure users searching for the legitimate/original domain variants. (location: page.html:69)

medium

brand impersonation

The page title references 'Tamilprint54.Art' while the actual domain is tamilprint55.art, and the page content announces 'Domain Changed' to TamilPrint55.Art. The site also impersonates the TamilRockers brand via meta description ('tamilrockers com', 'tamilrocker 2024') and cross-links to tamilprinttv.art. This network of incrementing numbered domains (.art TLD) is a well-known tactic to evade takedowns while hijacking the brand identity of a piracy network. (location: page.html:8-10, page.html:89-90, page.html:214)

medium

social engineering

The page prominently displays '(Bookmark Now!)' in the site header, socially engineering users into bookmarking the piracy site to ensure return visits and sustained exposure to the malvertising infrastructure embedded in the page. (location: page.html:67)

API

curl https://api.brin.sh/domain/tamilprint55.art

FAQ: how to interpret this assessment

Common questions teams ask before deciding whether to use this domain in agent workflows.

Is tamilprint55.art safe for AI agents to use?

tamilprint55.art currently scores 38/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.

How should I interpret the score and verdict?

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.

How does brin compute this domain score?

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.

What do identity, behavior, content, and graph mean for this domain?

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.

Why does brin scan packages, repos, skills, MCP servers, pages, and commits?

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.

Can I rely on a safe verdict as a full security guarantee?

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.

When should I re-check before using an entity?

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.

Last Scanned

March 4, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Disclaimer

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.

start scoring agent dependencies.

integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.