作者:rebot | 分类:模组
Minecraft 版本: 26.1 26.1.1 26.1.2
平台: fabric
标签: game-mechanics social utility
A client-side Minecraft mod that provides protection against client fingerprinting, tracking exploits, and other privacy focused features.
This is a passion project mostly built with AI.
Fake phishing sites and Discord servers has been distributing trojanized builds of OpSec. Only download OpSec from these official sources:
- Modrinth
- GitHub Releases
- CurseForge (updated less frequently)
Builds from anywhere else are not official and may be malicious.
If you're interested in servers or plugins that are using tracking related exploits then look in the Hall of Shame.
opsec-[minecraft_version]+[version].jar from the Releases page.minecraft/mods folderThe settings menu is accessible via the OpSec button in the multiplayer server selection menu header or via Mod Menu.
If settings are changed while connected to a server it is recommended to reconnect to the server to ensure changes are applied.
| Setting | Description |
|---|---|
| Spoof as vanilla | Enable/disable Spoof as Vanilla |
| Isolate Pack Cache | Enable/disable cache isolation |
| Block Local Pack URLs | Enable/disable local URL blocking |
| Bypass Server Pack Requirement | Configure server pack bypass behavior: • MANUAL (default): Default vanilla behavior on push. You can still toggle any server pack. • ASK: Server resource pack not applied but with consent screen to ask if the pack(s) should be applied • ALWAYS ON: Server resource pack not applied by default. You can still toggle any server pack |
| Strip Mod Shader Overrides | Enable/disable shader override stripping |
| Clear Cache | Delete all cached server resource packs |
| Key Resolution Spoofing | Enable/disable key resolution protection |
| Fake Default Keybinds | Return default vanilla keybind values instead of actual bindings |
| Meteor Fix | Disable Meteor Client's broken key resolution protection (only shown when Meteor is installed) |
| Signing Mode | Configure chat signing behavior: • OFF: Strip signatures (maximum privacy) • ON: Default Minecraft behavior • AUTO: Only sign when required (recommended) |
| Disable Telemetry | Enable/disable telemetry blocking |
| Setting | Description |
|---|---|
| Whitelist Mode | Select whitelist behavior: • BLOCK ALL: All mod content blocked • AUTO: Mods with network channels are automatically whitelisted (default) • CUSTOM: Manually select which mods to whitelist |
| Installed Mods | Toggle individual mods ON/OFF to exempt them from protection (CUSTOM mode only) |
| Setting | Description |
|---|---|
| Show Alerts | Display chat messages when tracking is detected |
| Show Toasts | Display popup notifications for important events |
| Log Detections | Log all detection events to game log for transparency |
| Debug Alerts | Show alerts for all probed keys, even unchanged ones |
| Debug Command | Enable the /opsec debug command. Off by default. |
| Setting | Description |
|---|---|
| Saved Accounts | List of added accounts with login/logout and remove buttons |
| Refresh All | Revalidate all account tokens (invalid tokens marked red) |
| Add Session Token | Add a new account using a session (access) token |
| Import | Import accounts from a JSON file |
| Export | Export accounts to a JSON file |
The /opsec command is off by default (enable it in Misc → Debug Command). When enabled, use /opsec in-game to access debug information:
| Command | Description |
|---|---|
/opsec |
Show available commands |
/opsec info |
Show overview of all tracked mods |
/opsec info <mod> |
Show details for a specific mod (translation keys, keybinds, channels, known packs, shaders) |
/opsec channels |
Show all tracked network channels with whitelist status |
Servers can query your client brand to detect whether you're running a modded client. OpSec provides true vanilla spoofing by blocking all mod key resolutions, network channels, and known-pack identifiers (whilst keeping vanilla ones).
Set to OFF by default to allow auto mod whitelisting (whitelist mods with network channels).
Based on LiquidBounce.
Server-required resource packs could be used to fingerprint client instance across accounts.
https://alaggydev.github.io/posts/cytooxien/
Instead of storing all resource packs in a shared cache (~/.minecraft/downloads/), OpSec creates separate cache directories for each account UUID.
Derived from ExploitPreventer by NikOverFlow
Malicious servers can send resource pack URLs that redirect to your local network to probe for local devices and services.
https://alaggydev.github.io/posts/cytooxien/
OpSec checks if a redirect or normal request targets a local address, then blocks the connection.
Servers can push required resource packs the client is forced to apply. Declining them or toggling required server resource pack(s) is impossible on vanilla client. And fake accepting them can be detectable via key resolution probing the client's resource pack key response.
Minecraft still accepts and downloads these packs as normal but OpSec lets you toggle the pack textures at the client level. The language file of the server resource pack is preserved because servers can probe translation keys (e.g. via {"translate": "some.pack.key"}) to detect whether the pack is actually applied, and a vanilla client with the pack loaded would resolve those keys to the pack-defined value.
With Opsec installed, server resource pack(s) appears as a normal user-toggleable entry in the resource pack menu so you can flip between stripped and fully-loaded.
Modes:
[Continue] / [Load Pack For Real].Some mods (e.g. Meteor Client) render their GUI with their own shaders loaded through Minecraft's resource manager. A forced server resource pack can overide the mod's own files to ship shaders under that mod to either blank the mod's GUI, crash the client with malformed shaders, or GPU DoS, which also fingerprints that the mod is installed.
OpSec strips shader overrides under assets/<mod>/shaders/ from server packs for any installed mod that isn't whitelisted, so the resource manager falls back to the mod's own bundled shaders. The rest of the pack still loads, so this keeps working even when a server forces the pack to make Bypass Server Pack Requirement unusable.
Vanilla (minecraft) shaders are never touched, and whitelisting a mod lets the server's shader override through.
Servers can send translatable text containing keys like key.attack or key.hide_icons in any server packet to probe which keys you have bound or mod UI elements your client can resolve. This can reveal the client's installed mods.
https://wurst.wiki/sign_translation_vulnerability
OpSec tracks when translation keys are being resolved during server packet processing and blocks Minecraft from resolving them based on your selected brand mode:
When Fake Default Keybinds is disabled, vanilla keybinds resolve to their actual values.
Spoofing mod keybinds (Returns raw keys/fallback value instead of keybind values):
[key.meteor-client.open-commands] '.'→'key.meteor-client.open-commands'
[key.meteor-client.open-gui] 'Right Shift'→'key.meteor-client.open-gui'
Spoofing vanilla keybinds with Fake Default Keybinds enabled (Returns default keybinds):
[key.hotbar.6] 'Q'→'6'
[key.hotbar.7] 'E'→'7'
[key.hotbar.8] 'R'→'8'
Legacy Meteor client a built-in key protection implementation which can lead to guaranteed detection with the key resolution probing.
The server can use a specially crafted translation key probe with a fallback value, instead of expecting the raw key from a vanilla client, its expecting the fallback value instead. Meteor client echos the raw key back instead of the server probe's fallback value.
When the server uses a sign exploit with fallback value on Meteor Client:
'key.meteor-client.open-gui' 'Right Shift'→'key.meteor-client.open-gui'
What a Vanilla response would actaully be:
'key.meteor-client.open-gui' '⟦FALLBACK⟧'→'⟦FALLBACK⟧'
OpSec's bandaid fix for Meteor is to blacklist the AbstractSignEditScreenMixin Mixin to disable Meteor's broken key resolution protection. Allowing OpSec's protection to take over, which already handle fallbacks correctly to match the Vanilla response.
For users that prefers ExploitPreventer's core protection implementation but still need OpSec's additional features, both can be installed alongside each other. Overlapping features are automatically disabled to let EP handle them, note that you would lose OpSec features such as channels spoofing. The following OpSec features are deferred to EP:
These settings are grayed out in the config screen but your saved preferences are preserved. If you remove EP later, they restore automatically.
Features that don't overlap remain fully functional: alerts, chat signing, account manager, telemetry blocking, Strip Mod Shader Overrides, and Meteor Fix.
Servers can query your registered network channels to detect which mods you have installed.
OpSec can conditionally block mod channels that are registered with the server to prevent detection.
This is enabled by default, its behavior is controlled by the mod whitelist and
Servers can probe your mod-injected pack identifiers that certain mods exposes to detect whether you're running a modded client or using certain mods.
OpSec intercepts the outgoing ServerboundSelectKnownPacks response and strips entries belonging to non-whitelisted mods. Real vanilla and auto whitelisted packs still pass through.
Only active on clients where Fabric's known-packs hook is present (MC 1.21.11+ with modern fabric-api).
Some mods require server communication to function properly (e.g., VoiceChat, Xaero's Minimap quick travel). The whitelist allows you to exempt specific mods from channel spoofing, key resolution protection, known-pack filtering, and shader override stripping.
Modes:
When the whitelist is active (AUTO or CUSTOM), Spoof as Vanilla will be disabled as exposing Fabric mods would need the client brand to match accordingly.
CUSTOM mode lists every installed mod so any mod can be whitelisted; AUTO mode only shows mods that register network channels.
Based on No Chat Reports.
Cryptographic signatures by default are attached to every chat messages. Removing them makes it impossible to track and associate your chat messages with your Minecraft client, and, by extension, Microsoft account.
Modes:
Based on Meteor Client.
Add Minecraft accounts with session tokens and switch between them without restarting the game.
Session tokens expire after some time. Use the Refresh button to check validity.
From No Chat Reports.
Minecraft collects and sends telemetry data to Mojang, including:
OpSec blocks telemetry sending to Mojang when telemetry blocking is enabled. Does not effect gameplay.
OpSec is a privacy tool designed to protect players from unwanted client fingerprinting and tracking. It is not intended or encouraged for use in bypassing server rules, evading bans, or gaining unfair advantages. Users are responsible for complying with the rules and terms of service of any server they connect to.
请登录后举报
暂无评论,抢个沙发吧~