context safety score
A score of 35/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The site presents itself as 'Honista' — a well-known modified/unofficial Instagram client — using Instagram branding language ('Full Feature Insta App') to attract Instagram users. The domain 'nakheelteam.cc' uses a .cc TLD (Cocos Islands) with no verifiable legitimacy, impersonating the Honista project to lure users into downloading an APK. (location: page.html:33-34, page.html:9)
malicious redirect
The page's sole call-to-action is a direct APK download link (https://dl.nakheelteam.cc/honista.apk) hosted on a subdomain of the same unverified .cc domain. Distributing a sideloaded Android APK outside the Google Play Store from an unknown domain is a high-risk vector for malware delivery, credential harvesting, or spyware targeting Instagram credentials. (location: page.html:36)
credential harvesting
'Honista' is a modified Instagram APK category known to be repacked with credential-stealing or session-hijacking payloads. The site mimics a legitimate app distribution page to trick users into installing an unofficial Instagram client that likely exfiltrates Instagram login credentials or session tokens. (location: page.html:36, page.html:33-34)
social engineering
The page uses minimal, trust-building design (professional HTML5 UP template, clean layout, 'Full Feature Insta App' framing, and a prominent 'Download Now' button) to create a false sense of legitimacy and urgency, lowering user suspicion before delivering a potentially malicious APK. (location: page.html:31-39)
brand impersonation
The page title is 'Honistagram Android App' and the footer reads '© Untitled. All rights reserved.' — a generic placeholder copyright notice — indicating the site was hastily assembled using a stock template without legitimate organizational identity, consistent with a fraudulent distribution site. (location: page.html:9, page.html:48)
curl https://api.brin.sh/domain/nakheelteam.ccCommon questions teams ask before deciding whether to use this domain in agent workflows.
nakheelteam.cc currently scores 35/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.