Cracked build detection
Download portals, torrent indexes, file hosts and mirrors are monitored for unauthorised copies of your software.
Solutions
Cracked builds, resold keys and repackaged installers do more than cost you a sale — they put malware in front of people who think they are running your product. AuthenScan monitors where your software is distributed without authorisation and enforces removals continuously.
The problem
Unauthorised software distribution is not only a revenue issue. A cracked installer is an ideal malware carrier, and when it is bundled with your name the support burden, the security incidents and the reputational damage land on you rather than on whoever repackaged it.
The distribution surface is wide: download portals, torrent indexes, forum threads, file hosts, messaging channels, and grey-market storefronts reselling keys obtained through fraud, regional arbitrage or stolen payment details.
Because each of those layers works differently, enforcement has to be matched to the layer — a file host takedown, a forum thread removal, a marketplace delisting or a key deactivation — and repeated, because re-upload is immediate.
Modified installers distributed through download portals and torrent indexes.
Tools defeating licensing, usually bundled with something considerably worse.
Storefronts selling licences obtained through fraud, chargebacks or regional arbitrage.
Shared or resold credentials operating well beyond the terms they were sold under.
Communities where links are posted, mirrored and refreshed as they are removed.
Downloads presented as your product that install something else entirely.
Why it matters
37%
Share of software installed on personal computers found to be unlicensed.
BSA Global Software Survey
$46.3B
Commercial value of that unlicensed software.
BSA Global Software Survey
216B
Visits to piracy sites worldwide in a single year.
MUSO, Piracy Trends and Insights
Figures are published by the sources named above and are provided for context. They are not AuthenScan performance claims.
What the monitoring covers
A release, a patch and a regional build are different artefacts. Tracking them separately is what makes enforcement precise.
Download portals, torrent indexes, file hosts and mirrors are monitored for unauthorised copies of your software.
Grey-market storefronts and resale channels are checked for keys sold outside your authorised distribution.
Communities, threads and messaging channels where links are shared, mirrored and refreshed.
Detections are tied to the specific release or patch, so you can see which builds leak and how quickly.
Downloads presented as your product but carrying something else are flagged as a security matter, not just a revenue one.
Enforced items stay under watch, and sources that repeatedly reappear are escalated rather than refiled endlessly.
How it works
Titles, versions, installers, official distribution channels and authorised resellers form the reference set.
Download sites, torrent indexes, file hosts, forums, channels and key marketplaces are covered continuously.
Each detection is confirmed and classified — cracked build, repack, key resale, licence abuse or malicious installer.
Notices go to the host, the platform, the forum operator or the marketplace, whichever actually removes availability.
Removed items remain monitored, and persistent sources are escalated with a documented history behind them.
Coverage
Sites distributing installers directly or through link aggregation.
Index listings and the mirrors that replace them after removal.
Communities where links are coordinated, mirrored and refreshed.
Grey-market storefronts reselling licences outside authorised distribution.
Result pages ranking for your product name plus crack, keygen or free-download terms.
Unauthorised or repackaged versions published under your product name.
What you receive
AuthenScan found and removed infringements we could never police manually.
FAQ
Cracked builds and repacks, key generators and licence patches, grey-market key resale, shared or resold credentials operating outside their terms, and fake installers distributed under your product name. Each is classified separately because the enforcement route differs.
Because cracked installers are a common malware delivery method. When the payload arrives under your product name, the resulting support tickets, security reports and reputational damage attach to you, not to whoever repackaged it — which is why malicious installers are flagged to your security team rather than treated as a revenue leak.
Yes, on two fronts. The storefronts themselves can be enforced against where keys were obtained fraudulently or resold in breach of your terms, and the findings tell you which supply routes are being exploited, so keys can be deactivated and the source closed off upstream.
Yes, and it is often the most immediately actionable output. Detections are tied to specific versions and patches, so you can see which releases leak, how quickly after publication, and whether a particular regional or partner build is the recurring source.
The same way as in any anti-piracy programme: enforced items stay in the monitoring set permanently, re-uploads are refiled promptly, and sources that reappear repeatedly are escalated with an accumulated history rather than processed as fresh cases each time.
No, and any provider who says otherwise is selling something. What it does is materially reduce availability through the channels ordinary users actually reach — search results, download portals, mainstream forums and key marketplaces — which is where the commercial impact and the malware risk are concentrated.
