Tech
A Typosquatted Gem Almost Shipped, Caught by Luck: A Ruby Supply Chain Security Playbook
The exposure
A teammate opened a PR adding a small utility gem. The name looked right at a glance — one transposed character from a popular package. It passed our tests. On a normal Friday it would have merged. Someone caught the typo in review by luck, not process, and the gem turned out to be a typosquat whose extconf.rb ran code at install time that had no business running.
"By luck, not process" is the phrase that reframes this from an anecdote into a security finding. Ruby supply ...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to