A C/C++ API that allows developers to write programs to communicate with the driver.
A background job or database trigger that enforces expiration. oblitum/interception
, is a low-level input library for Windows that allows developers to intercept and modify keystrokes and mouse movements. While it is a legitimate tool used for remapping keys or creating macros, it is frequently flagged by anti-cheat systems (like FACEIT, Vanguard, and EA Anti-Cheat) as a "forbidden" or "prohibited" driver. If you are seeing errors such as A C/C++ API that allows developers to write
# Python example using a decorator/interceptor class OblitumInterceptor: def __init__(self, rules): self.rules = rules # e.g., "credit_card": "redact", "ssn": "hash" def intercept(self, data: dict) -> dict: for field, action in self.rules.items(): if field in data: if action == "redact": data[field] = "[REDACTED]" elif action == "hash": data[field] = hashlib.sha256(data[field].encode()).hexdigest() elif action == "tokenize": data[field] = self.tokenize(data[field]) # Tag metadata for oblitum layer data["_oblitum_expiry"] = time.time() + 3600 # 1 hour TTL return data While it is a legitimate tool used for
| Problem | Without Oblitum/Interception | With Pattern | |--------|-------------------------------|---------------| | PII in logs | Accidentally logged credit cards, emails | Intercepted & redacted before write | | GDPR right to erasure | Complex manual deletion across backups | Automatic field-level expiry | | Debugging prod issues | Full data capture (high risk) | Anonymized interception + trace IDs | | Insider threat | Long-lived sensitive fields | Short TTL on decrypted values |