A force-push is a Git operation that replaces the history of a remote branch with your local branch state. Instead of adding new commits on top of what is already there, it can rewrite or remove commits that other people expect to see. This is why it is powerful and risky: it can hide evidence of work, discard reviewer changes, or make a branch look clean after suspicious edits.
In cyber security, force-push matters because Git history is part of the trust model for software development. Defenders rely on branch protection, code review, and immutable-looking history to detect tampering and coordinate safe changes. In supply-chain attacks or abuse attempts, an attacker may use a force-push to erase a malicious commit, replace a branch with a safer-looking version, or rewrite the record after being challenged. Strong permissions and protected branches reduce the damage by preventing unauthorized history rewrites.