Repository navigation
trivy.dev appears parked since Nov 3 21:34 UTC: get.trivy.dev is NXDOMAIN, breaking install.sh and setup-trivy #11533
Closed
mitchnielsen
started this conversation in
Bugs
Replies: 5 comments
|
0 replies
|
Trivy extension in the Azure DevOps pipeline is failing Starting Trivy task... |
0 replies
|
Looks like someone forgot to renew the domain trivy.dev 😢 |
0 replies
|
We've renewed the |
0 replies
|
this was pretty dangerous, someone malicious could create a clone of trivy and put a malicious tar.gz there to fetch your creds... |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description
trivy.devappears to have been parked. The registry's RDAP record showslast changedat 2026-11-03 21:34:00 UTC, with nameserversns75andns76.domaincontrol.com. Since then,get.trivy.devhas returned NXDOMAIN on most public resolvers I tried, and the delegated nameserver has no record for it.contrib/install.shdownloads the release tarball from this host, so installs fail. That includesaquasecurity/setup-trivy, andaquasecurity/trivy-actionthrough it.Evidence as of about 23:37 UTC on Nov 3:
get.trivy.devreturns NXDOMAIN from8.8.8.8,1.1.1.1, and208.67.222.222, and fromns75.domaincontrol.com.9.9.9.9gave mixed answers, probably from its cache.bristol.ns.cloudflare.comstill returns104.26.2.26,104.26.3.26, and172.67.72.165, so the record looks like it wasn't carried over.13.248.213.45and76.223.67.189fortrivy.dev. The new IP fails TLS fortrivy.dev, and over HTTP it redirects to/lander, which looks like a parking page.auto renew period, and expiry 2027-10-29.Machines with a cached DNS answer still reach the site, so this can look fine locally.
Desired Behavior
get.trivy.devresolves on public DNS, andcontrib/install.sh,setup-trivy, andtrivy-actioninstall Trivy normally.If a tarball download fails,
install.shshould print an error that names the URL. It could also fall back to GitHub releases, which still serve the same tarball.Actual Behavior
trivy-actionjobs fail while installing Trivy, before any scan runs:Exit code 6 matches curl's "could not resolve host". Our failures began around 21:34 UTC, first intermittently and then on every run.
The installer calls curl with
-sand runs underset -e, so nothing in the log points to DNS or toget.trivy.dev. The last visible line mentions GitHub, which makes this look like a GitHub problem.We're using
trivy-actionated142fd0673e97e23eac54620cfb913e5ce36c25withsetup-trivyv0.2.6 and Trivy v0.70.0.Reproduction Steps
Target
None
Scanner
None
Output Format
None
Mode
None
Debug Output
Operating System
MacOS, Linux
Version
Checklist
trivy clean --allAll reactions