[WordPress] 外掛分享： Init Content Protector – Anti-Copy, Anti-Scrape, Encrypt-All

內容簡介

Init Content Protector 是一款強大且輕量的外掛，旨在保護您的文章內容，防止未經授權的複製、抓取工具和瀏覽器開發者工具的檢查。此外掛是 Init Plugin Suite 的一部分，專為 WordPress 開發者設計。

【主要功能】
• JavaScript 基於的複製保護
• 進階開發者工具封鎖
• 反截圖/反抓取工具檢測
• 完整的 AES-256 內容加密
• 自訂加密金鑰每個網站
• 自訂內容選擇器支援

外掛標籤

開發者團隊

原文外掛簡介

Init Content Protector is a powerful yet lightweight plugin that safeguards your post content from unauthorized copying, scraping tools, and inspection via browser developer tools.
This plugin is part of the Init Plugin Suite — a collection of minimalist, fast, and developer-focused tools for WordPress.
GitHub repository: https://github.com/brokensmile2103/init-content-protector
Features:
– JavaScript-based copy protection (blocks selection, right-click, print, DevTools access)
– Advanced DevTools blocking (optional, powered by the third-party disable-devtool library) — detects DevTools being opened through multiple methods, not just keyboard shortcuts, and closes or redirects away from the tab
– Anti-screenshot / anti-scraping-tool detection (optional, powered by “Init AntiSnap 6.0”) — recognizes the evenly spaced, step-by-step scrolling of scroll-and-stitch capture tools and DevTools full-size captures, and briefly blurs the page with a warning
– Full AES-256 content encryption with client-side decryption via the browser’s built-in Web Crypto API (CryptoJS is only loaded on sites not served over HTTPS, or on demand as a fallback)
– Inline delivery (default, simple) or Enhanced delivery (fetches the key via a REST API endpoint after page load — keeps it out of cached/static HTML, cache-plugin friendly)
– Encryption is done fresh on every request (about a third of a millisecond), so members-only or per-user content can never be served to the wrong visitor from a cache
– Fails open gracefully on hosts missing OpenSSL/PBKDF2 support, instead of breaking the page
– Optional Headless Browser Detection: withholds decryption from sessions that look like Puppeteer/Playwright/Selenium, scored across several client-side automation signals so no single false-positive blocks a real visitor
– Keyword cloaking using CSS pseudo-elements (whole words only, Unicode aware, never inside HTML attributes or code blocks)
– Invisible noise injection to confuse crawlers — only ever injected into plain text, never inside HTML tags or inside