Lots more technical research about the actual attack and how it worked here: https://socket.dev/blog/trivy-under-attack-again-github-acti...
Disclosure: I’m the founder of Socket.
Trivy ecosystem supply chain temporarily compromised
31–40 of 42 posts
Re: Trivy ecosystem supply chain temporarily compromised
#32The irony of your vulnerability scanner being the vulnerability.
Ever heard of IBM QRadar SIEM?
Re: Trivy ecosystem supply chain temporarily compromised
#33Re: Trivy ecosystem supply chain temporarily compromised
#34Sounds like Trivy is still compromised:
https://www.aquasec.com/blog/trivy-supply-chain-attack-what-...
Re: Trivy ecosystem supply chain temporarily compromised
#35Lots more technical research about the actual attack and how it worked here: https://socket.dev/blog/trivy-under-attack-again-github-acti... Disclosure: I’m the founder of Socket.
Great analysis!
The Go binary was also compromised, but there's almost no information what the compromised binary did. Did it drop a python script? Did it do direct scanning?
If trivy docker image was used, what's the scope (it does not include python).
Re: Trivy ecosystem supply chain temporarily compromised
#36This attack seems predicated on a prior security incident ( https://socket.dev/blog/unauthorized-ai-agent-execution-code... ) at Trivy where they failed to successfully remediate and contain the damage. I think at this time, Trivy should’ve undertaken a full reassessment of risks and clearly isolated credentials and reduced risk systemically. This did not happen, and the second compromise occurred.
They did a lot of what you describe, although perhaps not well enough.
It seems not enough again, as their Docker images have now been compromised (as of March 22nd, 2026): https://github.com/aquasecurity/trivy/security/advisories/GH...
Re: Trivy ecosystem supply chain temporarily compromised
#37Мы позвали царского дегустатора проверить суп на яд, но яд оказался на его ложке.
Re: Trivy ecosystem supply chain temporarily compromised
#38To be clear, this is a supply chain attack on everyone that uses Trivy, not a supply chain attack on Trivy. It was a direct attack on Trivy, exploiting components that Aqua had full control and responsibility for. The term “supply chain attack” has a connotation of “ it’s not really my fault, it was my dependencies that got compromised ”. Of course, every entity is ultimately accountable for its own security, includi…
The term “supply chain attack” has a connotation of “it’s not really my fault, it was my dependencies that got compromised”.
In my experience that is definitely not true, and I've never heard anyone use it that way. Even though you are correct in who the target was.
Re: Trivy ecosystem supply chain temporarily compromised
#39To be clear, this is a supply chain attack on everyone that uses Trivy, not a supply chain attack on Trivy. It was a direct attack on Trivy, exploiting components that Aqua had full control and responsibility for. The term “supply chain attack” has a connotation of “ it’s not really my fault, it was my dependencies that got compromised ”. Of course, every entity is ultimately accountable for its own security, includi…
A supply chain attack is an attack on a provider of a solution that is then deployed further. The issue with a supply chain attack is that the ultimate victim brings in trusted software that was compromised upstream.
Re: Trivy ecosystem supply chain temporarily compromised
#40Still compromised: https://socket.dev/blog/trivy-under-attack-again-github-acti...
This is a very old vulnerability, and to see companies falling for it is mental.
The year is 2026 and companies are still using tag over hash. It is well known that you can release different code under the same tag without alerting users.