alt.hn

3/20/2026 at 3:30:07 AM

Trivy ecosystem supply chain briefly compromised

 https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23

by batch12

3/22/2026 at 8:25:31 AM

To 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, including assigning a level of trust to any dependencies, so it’s ultimately no excuse, but getting hit by a supply chain attack does evoke a little more sympathy (“at least I did my bit right”), and I feel like the ambiguous wording of the title is trying to access some of that sympathy.

by jl6

3/22/2026 at 2:11:56 AM

This 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.

by Shank

3/22/2026 at 4:55:29 AM

They did a lot of what you describe, although perhaps not well enough.

by NewJazz

3/22/2026 at 3:56:32 AM

I don’t think “briefly compromised” is accurate. The short span between this and the previous compromise of trivy suggests that the attacker was able to persist between their two periods of activity.

by woodruffw

3/22/2026 at 3:41:40 AM

Don't forget to pin your GitHub Actions to SHAs instead of tags, that may or may not be immutable!

by AdrienPoupa

3/22/2026 at 4:00:08 AM

Frustratingly, hash pinning isn’t good enough here: that makes the action immutable, but the action itself can still make mutable decisions (like pulling the “latest” version of a binary from somewhere on the internet). That’s what trivy’s official action appears to do.

(IOW You definitely should still hash-pin actions, but doing so isn’t sufficient in all circumstances.)

by woodruffw

3/22/2026 at 5:18:44 AM

That's true. This specific attack was mitigated by hash pinning, but some actions like https://github.com/1Password/load-secrets-action default to using the latest version of an underlying dependency.

by AdrienPoupa

3/22/2026 at 1:35:52 PM

This attack was not mitigated by hash pinning. The setup-trivy action installs the latest version of trivy unless you specify a version.

by cpuguy83

3/22/2026 at 2:47:18 PM

Oh, I was referring to `aquasecurity/trivy-action` that was changed with a malicious entrypoint for affected tags. Pinned commits were not affected.

by AdrienPoupa

3/22/2026 at 4:49:55 AM

I'm pretty sure the trivy action does not do that.

by NewJazz

3/22/2026 at 5:20:25 AM

FWICT, it pulls the latest version of trivy by default. If that latest tag is a mutable pointer (and it typically is), then it exhibits the problem.

by woodruffw

3/22/2026 at 12:31:56 PM

> credential rotation was performed but was not atomic (not all credentials were revoked simultaneously).

How do you simultaneously revoke all credentials of all your accounts spanning multiple services/machines/users?

by duckmysick

3/22/2026 at 6:33:40 AM

The irony of your vulnerability scanner being the vulnerability.

by swq115

3/22/2026 at 5:15:33 PM

Ever heard of IBM QRadar SIEM?

by real_joschi

3/22/2026 at 5:25:36 PM

Yes... Any more context? Were they leaking data?

by NewJazz

3/22/2026 at 12:30:29 AM

Are the spam comments all from compromised accounts, presumably compromised due to this hack?

I only clicked on a handful of accounts but several of them have plausibly real looking profiles.

by snailmailman

3/22/2026 at 2:12:37 AM

what comments?

by wswin

3/22/2026 at 2:54:11 AM

Ah, I think the HN post was merged. My original comment was in response to this related github discussion: https://github.com/aquasecurity/trivy/discussions/10420

There are hundreds of automated spam comments there from presumably compromised accounts. The new OP is much more clear regarding what has happened.

by snailmailman

3/22/2026 at 12:53:45 AM

Briefly?

"Trivy Supply Chain Attack Spreads, Triggers Self-Spreading CanisterWorm Across 47 npm Packages"

https://it.slashdot.org/story/26/03/22/0039257/trivy-supply-...

by MilnerRoute

3/22/2026 at 2:09:56 AM

"Briefly" is doing a lot of work there. Pre-deploy scans are useless once a bad mutation is actually live. If you don't have a way to auto-revert the infrastructure state instantly, you're just watching the fire spread.

by zach_vantio

3/22/2026 at 2:25:28 AM

Seriously. All credentials compromised that it can see. It's active in CI/CD pipelines and follow on attacks are happening.

by brightball

3/22/2026 at 8:45:57 AM

yeah, we keep learning the same lesson: the tool that audits your supply chain is the single best target for compromising it

by 4riel

3/22/2026 at 1:48:20 AM

Pretty ironic that the security tool is insecure

by RS-232

3/22/2026 at 2:40:41 AM

You must be new to this. The median line of code in a security tool is materially less secure than the median line of code overall in the industry.

by tptacek

3/22/2026 at 7:50:57 AM

Similarly one of our biggest causes of power outages when I worked with a DC was the UPSes. And the biggest causes of data loss were the hardware RAID controllers. Feels like there's a fundamental law lurking under this stuff.

by regularfry

3/22/2026 at 1:30:11 PM

As the complexity of a system increases, the number of single points of failure also tends to increase. Sometimes you can make sure that several subsystems need to fail before the whole system fails. Often, the best you can do is swap one SPoF (e.g. unreliable power grid) for another, more robust SPoF (unreliable UPS).

by snackbroken

3/22/2026 at 5:09:17 AM

this is painfully accurate. ive worked in security for years and the tools we trust the most get the least scrutiny because everyone assumes "well its a security tool, it must be secure." the irony is these tools usually run with the highest privileges in the pipeline. trivy sits in CI with access to every secret in your environment and nobody questions it because its supposed to be the thing protecting you.

by CoderLuii

3/22/2026 at 1:14:39 AM

[dead]

by robutsume

3/22/2026 at 11:40:33 AM

[dead]

by qkitzero