Take back control.

Protection solutionsDMCA takedown serviceGoogle copyright removal serviceCopyright monitoring servicePublisher anti-piracy serviceCopyright protection for creatorsImage licensing & attribution serviceSoftware piracy takedown service
Knowledge hubCopyright protection guidesCopyright essentialsTakedown field guidesContent protection
Company & standardsAbout LINK-BUSTERFees & service scopeResponsible enforcementContact

Independent copyright protection.
Hong Kong · United States

Software piracy: document the claim without downloading risk

Document suspected software piracy safely with product, version, licence, listing, and visible-page evidence - Without downloading or running unknown files.

A sealed software package and a suspicious file tile examined from behind a clear protective glass partition Conceptual imagery generated with OpenAI. Not documentary evidence.

Document the listing without executing the file

Do not trade system security for a larger list of suspected software copies.

Safe software piracy evidence checklist

The product owner identifies the official version and licence. The reviewer documents the listing or repository without running an unknown file. The recipient assesses the report.

  1. Official product

    Keep the product name, version, release channel, licence, and rights owner.

  2. Observed location

    Save the exact listing, repository, page, claims, and visible file details.

  3. Known exceptions

    Identify open-source parts, authorized mirrors, resellers, tutorials, and security-reporting needs.

Separate a suspicious listing from a verified copy

A page offering a cracked product can be fraudulent, malicious, or inaccurate. Record what the page actually contains and what you can substantiate.

A product-name match alone does not prove that the site distributes your code. Keep suspect listings separate from cases with sufficient evidence for a copyright claim.

Define the protected product precisely. Record product and company names, version, release channel, copyright owner, licence terms, official download locations, and the code, documentation, artwork, or packaging believed to be copied. Separate open-source components and third-party libraries from proprietary material. A familiar interface or matching product name alone does not establish reproduction of protected software expression.

Preserve product and rights metadata

Record official product names, versions, release channels, licensing terms, and the entity holding the relevant rights. Check whether any components are open source or redistributed under permission. A review or compatibility tutorial mentioning your software is not the same as an unauthorized distribution.

Capture page-level evidence without fetching the payload. Save the listing URL, repository or file page, visible filenames, version claims, screenshots, seller or uploader identity, timestamps, and any checksum published by the page. Record what was not verified. A label such as cracked or full version can support triage, but it does not prove the contents of a file that was never safely examined.

Avoid creating a new security incident

Do not run unknown installers or cracked executables to confirm a suspicion. Where forensic analysis is necessary, use appropriately isolated specialist processes and authorized personnel. A routine rights workflow should not fetch arbitrary files from untrusted URLs or expose internal systems to them.

Use a controlled escalation path when binary inspection is necessary. Define who is authorized, which isolated environment and security controls apply, how the sample will be stored, and how results will be documented. Routine content reviewers should not run unknown installers on work devices. Malware, credential theft, and impersonation concerns may require security or platform-abuse handling separate from copyright.

Report the available evidence honestly

Explain the observed distribution, identify precise URLs, and disclose relevant limits in what was verified. Use an appropriate platform abuse route when the substantiated issue is impersonation or malware rather than copied code. Track provider decisions and maintain a suppression list for authorized mirrors and distributors.

Match the report to the evidence available. A repository containing copied source files, a marketplace listing using product artwork, and a page linking to an unverified archive are different fact patterns. Identify the exact material the recipient can locate and the specific right asserted. Preserve declined or inconclusive decisions so the same uncertain file is not repeatedly presented as a verified piracy event.

Sources & further reading

This guide draws on the primary references below. Requirements vary by recipient and jurisdiction; check the current official process before acting.

General information, not an individualized legal opinion. For a disputed claim or litigation deadline, consult qualified counsel. Read our editorial and correction policy.

More from content protection

Publisher anti-piracy workflow: a practical guide

Build a publisher anti-piracy workflow that tracks titles, editions, rights, licensed distribution, suspected copies, priority, and verified outcomes.

Read guide

Protect an online course without targeting your students

Protect online courses by mapping lessons and source files, distinguishing legitimate student access from redistribution, and preserving lesson-level evidence.

Read guide

Image theft evidence guide for photographers

Document suspected image theft with original files, authorship records, licence history, exact image and page URLs, context, and a proportionate next step.

Read guide

Ready to protect
what you created?

Choose ongoing monitoring, help with a specific infringement, or an attribution and licensing assessment.

Choose a service