A developer account compromise occurs when an attacker gains unauthorized access to an identity used by a software maintainer or publisher. With access to release systems, the attacker may replace or add downloadable files without changing the project’s source code. This can turn a trusted download channel into a way to distribute malware.
In cyber security, these compromises are a software supply-chain risk because users may trust artifacts published under a legitimate project or vendor account. Defenses include multi-factor authentication, tightly limited publishing permissions, protected release workflows, and signed artifacts that users can verify. If a release may have been tampered with, organizations should check installed versions, remove affected files, rotate secrets accessible to them, and review relevant authentication logs.