Is vipey.co safe?

suspiciouslow confidence
35/100

context safety score

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

identity
60
behavior
100
content
0
graph
30

7 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

high

social engineering

Site uses aggressive get-rich-quick language ('Hasilkan Jutaan Rupiah per Minggu' / 'Earn Millions of Rupiah per Week', 'Gratis, mudah, dan langsung bisa mulai cuan') to lure users into registering as publishers and uploading content, a classic social engineering tactic to harvest user accounts and content. (location: page.html: <section> banner overlay, <h2> and <h3> elements; page-text.txt visible text)

high

credential harvesting

The site presents a login page (/login) and a publisher registration flow (/register?ref=publisher) with no observable brand legitimacy, domain age unknown, WHOIS privacy redacted. The registration funnel is designed to collect user credentials and personal information under the pretense of monetization. (location: page.html: <a href='/login'>, <a href='/register?ref=publisher'>; metadata.json: domain_age_days=null, privacy_redacted=null)

medium

brand impersonation

An external image is hotlinked directly from assets.pikiran-rakyat.com (a major Indonesian news outlet) to lend visual legitimacy and implied association with a reputable media brand without authorization, creating a false sense of credibility. (location: page.html: <img src='https://assets.pikiran-rakyat.com/crop/0x0:0x0/1200x675/photo/2024/01/12/1793837542.jpg'>)

medium

hidden content

Multiple suspicious meta tags with hash-like names and identical name/content values are present (e.g., name='83c1a3a837d3dd8fa2f3fede1099ff405dd2fb2d' content='83c1a3a837d3dd8fa2f3fede1099ff405dd2fb2d'), along with a 'clickaine-site-verification' tag. These are non-standard meta tags indicative of ad-fraud network registration (Clickaine is a known push-notification/popunder ad network associated with malvertising) and hidden tracking/fingerprinting infrastructure. (location: page.html: <meta name='clickaine-site-verification'>, <meta name='83c1a3a837d3dd8fa2f3fede1099ff405dd2fb2d'>, <meta name='a49b024a75a9fc68ed4b1462f2f0b9f3e0652121'>)

medium

malicious redirect

The site is verified with Clickaine, a push-notification and popunder ad network widely documented in malvertising campaigns. Users interacting with the site (especially clicking upload or register) are likely subjected to forced redirects, popunders, or push-notification subscription prompts leading to malicious destinations. (location: page.html: <meta name='clickaine-site-verification' content='169b0b63b16cef2dd79d0986d61bccee4a907ab47ee721c4ee3cb910af6bc196e25e7388e28e56095f36ec187f6e90378f1046da5894a82506487f20d26c9173'>)

high

phishing

The site mimics a legitimate video monetization platform (similar in concept to YouTube Partner Program) targeting Indonesian-speaking users with promises of large weekly earnings to lure them into submitting account credentials and personal data. Domain age is unknown, WHOIS is privacy-redacted, and the site has no verifiable organizational identity, matching a phishing site profile. (location: metadata.json: domain_age_days=null, privacy_redacted=null; page.html: full page structure with /login and /register?ref=publisher flows)

API

curl https://api.brin.sh/domain/vipey.co

FAQ: how to interpret this assessment

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

Is vipey.co safe for AI agents to use?

vipey.co 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.

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.