What our analysis found

Pocket Universe, used by 100,000 people, is rated caution by Extension Auditor. Our code review reported 2 findings (1 high, 1 medium), led by other. Its permissions mean it can inject scripts into pages and can observe network requests.

Key findings

• high· other —The bundled manifest declares `sidePanel` (line 38) and `offscreen` (line 39) permissions that are absent from the published CWS manifest. The published manifest additionally lists `file://*/*` in host_permissions, which the bundled manifest omits. Because `sidePanel` and `offscreen` cannot be acquired at runtime—they must be in the installed manifest—users approved a narrower permission scope than what the extension actually holds. This divergence between disclosed and actual permissions is a meaningful integrity concern for an extension that handles wallet transaction signing.
• medium· obfuscation —The build system injects documentation strings explicitly asserting that the visible API domain strings are decoy 'honeypot' aliases and that real network traffic is domain-fronted through Cloudflare Workers in a way designed to evade network monitoring. Companion comments in aster-consent-bridge. (lines 447–452, 1042–1043) make parallel claims: visible postMessage event types deliver only 'synthetic honeypot data' while real inter-context messaging uses ECDH-derived encrypted BroadcastChannel, and visible storage keys are write-only honeypots while real storage uses opaque HKDF-derived IndexedDB identifiers. These strings are dead code (assigned to unused variables), but the explicit intent to present false artifacts to code analysis tools—rather than merely encrypting communications for security—is an unusual anti-analysis posture that cannot be reconciled with the visible source alone. Without the background service worker the claims are unverifiable.

Pocket Universe is a well-established Web3 security extension (4+ years, 100K users, Google, ML score 0.00) whose core function—intercepting transactions to warn on scams and collecting builder fees from DeFi protocols—explains its broad permissions and all-site content scripts. Two concrete concerns prevent a clean clearance: (1) the bundled manifest includes `sidePanel` and `offscreen` permissions absent from the published CWS manifest, meaning the extension operates with elevated permissions beyond what users approved at install time; (2) build-transform comment strings in relay-website. and aster-consent-bridge. explicitly state that visible API domains, message type strings, and storage keys are injected as 'honeypot' decoys and that real traffic, messaging, and storage use encrypted, opaque channels designed to be undetectable by network monitoring and code analysis—language that goes well beyond standard anti-tamper hardening. The third-party likelihood score () and corroboration signals (publisher trust, user count, age) favor a legitimate product, but the anti-analysis documentation and permission mismatch warrant a suspicious rather than benign rating, particularly without access to the background service worker where the claimed hidden behavior would reside.