GoPlus Security

Organizations should consider alternative providers or additional controls when any of the following apply:

1. Procurement requires independently verifiable enterprise compliance artifacts

• If SOC 2 Type II or ISO 27001 documentation is a mandatory gating criterion and public attestations are required, this vendor’s public footprint on those attestations was not clear in this research pass.

2. Primary need is AML/compliance and investigations

• The product is focused on scam/phishing and token risk signals; AML/investigations programs are more commonly addressed by Chainalysis or TRM Labs.

3. Primary requirement is human-auditor signed smart contract audit reports

• Vendor tooling marketed as fast or AI-assisted may complement, but not replace, formal third-party audits for high-TVL protocols.

4. Risk tolerance for false positives is very low

• Real-time risk firewalls can create conversion friction. Organizations with low tolerance for false positives should validate precision via pilots and adjust UX accordingly.

5. Extremely high throughput requirements without a confirmed SLA

• Where high QPS and bounded latency are contractual requirements, procurement should require explicit SLAs and conduct load testing prior to relying on the service in production.

1. Security and compliance transparency gaps

• Public documentation of SOC 2 or ISO certifications and enterprise security attestations was not found in this research pass.

2. Review and validation gaps

• Limited presence on mainstream SaaS review platforms increases the effort required to benchmark customer satisfaction and support outcomes.

3. Extension trust model and code transparency

• The vendor roadmap indicates an intention to open-source the browser extension; until that is completed, some security teams may treat the extension as higher risk.

4. Rate limiting and free-tier scalability

• The free API rate limit (30 calls/min) may not support high-volume production traffic without migrating to paid tiers or batching calls.

Mainstream review platforms were not productive in this pass. The most accessible review-like sources were extension indexers and community forums. These sources can be helpful for initial signal but require caution due to potential manipulation or bias.

Reported positive sentiment (extension-oriented):

• Some extension index and aggregator pages summarize the extension positively for detecting phishing and malicious contracts; these are site-generated summaries and are not replacements for verified user reviews.

Examples assessed as potentially promotional or low-signal:

• Community posts and announcement-style threads observed in forums or subreddits often reflect vendor or partner announcements rather than independent user evaluations.

Common selection drivers cited in vendor materials and commissioned research include:

• Broad chain support and wallet/dApp integrations.
• Availability of free or limited access APIs and SDKs for initial testing.
• Near-real-time risk intelligence across tokens, addresses, phishing, approvals/signatures, and transactions.

Note: Some of the materials that describe these selection drivers are vendor-commissioned or vendor-provided; verification via independent sources or pilots is recommended.

Direct negative product reviews were scarce in accessible sources; criticisms and concerns identified in this research pass include:

• Trust and verification challenges associated with browser extensions (store moderation, fake reviews, extension supply-chain risks).
• Operational risk in relying on third-party risk scores (false positives and false negatives that can create user friction or block legitimate transactions).
• Limited transparency when extension code or full methodologies have not yet been fully open-sourced.

Contextual sources on extension risks and review reliability are cited in the Sources section.

• Company size: Startups to mid-market Web3 teams (small-to-mid engineering organizations) integrating wallet/dApp security intelligence; larger enterprises (wallets/exchanges) may be appropriate if compliance and security posture are validated through vendor diligence.
• Industries: Web3 wallets, DeFi, exchanges, NFT marketplaces, on-chain games, prediction markets, and aggregators.
• Personas: Product security engineers, platform security engineers, wallet/dApp product managers responsible for fraud and scam reduction, and trust/safety teams.

GoPlus Security is a security infrastructure layer for Web3 that provides real-time security intelligence (risk signals about tokens, addresses, NFTs, dApps, phishing sites, approvals, signatures, and transactions) via APIs/SDKs and end-user products (a browser extension and an app). The product is designed to reduce on-chain scam, phishing, and theft risk by adding automated risk detection into wallets, dApps, and user workflows.

Key product lines and components commonly referenced:

• GoPlus Security Intelligence (APIs/SDKs): token security, malicious address, NFT security, approvals, signatures, dApp security information, phishing site detection, rug-pull detection (beta), transaction simulation, etc. (documentation available from the vendor).
• SafeToken Protocol: templates and liquidity/locking mechanisms focused on token issuance (SafeToken Factory/Locker).
• End-user tooling: browser extension and a mobile app described as a security hub.

Sources: Official vendor documentation and product whitepaper.

Primary audience:

• Web3 wallets, dApps, exchanges, aggregators, and infrastructure providers that require near-real-time risk scoring and detection embedded into transaction flows.
• Token projects and DeFi protocols seeking token security checks, safer token issuance templates, lockers, and automated audit-like checks.
• End users who install a browser extension to detect risky interactions.

Positioning:

• The vendor describes the product as a decentralized, permissionless, user-driven security network rather than a traditional centralized security vendor.

Sources: Vendor documentation and public research.