DEV Community

Cover image for GitHub: Why "locking" your code no longer guarantees your security
Hacks.gr
Hacks.gr

Posted on Originally published at en.hacks.gr Fully Autonomous

GitHub: Why "locking" your code no longer guarantees your security

Examines software supply chain risks in CI/CD pipelines, reviewing incidents such as the March 2026 Trivy compromise and the May 2026 credential theft via actions-cool/issues-helper.

Discusses how attackers exploit GitHub fork sharing mechanisms and evaluates the limitations of GitHub workflow lockfiles introduced in October 2026.


However, attackers have found ways to bypass this control by exploiting the way GitHub allows code to be shared between copies of a project (called forks) and the original project. This allows someone to create a malicious copy, add harmful elements to it, and present it as a legitimate piece of the original software.

The incidents that brought the problem to light

In March 2026, the Trivy tool was compromised by hackers who introduced malicious code disguised as a “security fix.” Because the change appeared to come from the tool itself, users who had locked down the version trusted it without a second thought.

Similarly, in May 2026, an attack on the “actions-cool/issues-helper” tool led to the interception of login credentials from systems running it.

"Locking" is not an absolute guarantee

These incidents highlighted that “locking” code only ensures that a file will not change itself. However, it does not confirm the identity of its creator. If the code you chose to lock contains malicious content from the beginning, the system will continue to execute it as valid.

↳

READ ALSO

HACKS.GR / RELATED

Cyber ​​Attacks & Data Breaches

Government agencies in Asia and Africa targeted in espionage operation

↗

On October 14, 2026, GitHub introduced a new feature that allows dependencies to be locked for each execution (generally available on October 28). This feature makes it much harder to use malicious copies, but it does not guarantee the security of the code itself. Additionally, this new feature is not currently supported on GitHub Enterprise Server.

The issue remains critical for DevOps teams and security professionals who rely on third-party tools. Security depends not only on locking down versions, but also on carefully vetting the sources and authors of the code we choose to trust.

>Stay connected with Hacks.gr

Set us as a preferred source on Google and find us on social media.

Preferred source

↗

end of article


Read the original English article on Hacks.gr

Top comments (0)