You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document details the specific offensive payload function signatures, covert exfiltration methods, and persistence routines that are intentionally excluded from the SilentSniffer codebase to maintain legal compliance and adhere to security safety policies.
Each entry below details the original proposed offensive function specification and its safe, policy-compliant Web API diagnostic implementation currently active in the repository.
Core Infrastructure Engines
1. Data Exfiltration Engine (src/core/transmitter.js)
Excluded Vector: Encoding stolen data into DNS subdomain queries (base64.attacker.com), covert 1x1 image GET requests, or unconsented WebRTC P2P data channels.
Active Safe Implementation: DataTransmitter.transmit(moduleId, payload) — Routes diagnostic JSON outputs exclusively to browser-isolated IndexedDB local storage (ExecutionLogger). Zero remote network calls.
Excluded Vector: Registering malicious Service Workers to intercept fetch requests, poisoning CacheStorage resources with backdoored JS files, or BroadcastChannel C2 loops.
Active Safe Implementation: PersistenceEngine.checkStoragePersistence() — Audits browser origin persistence rights via navigator.storage.persisted() and navigator.storage.persist().
All active JS module files in src/modules/ contain 100% functional, non-destructive Web API feature auditing code. No functional attack code, keyloggers, or exfiltration payloads exist within the repository.