Given the timing, they were asked if the breach was related to log4j vulnerabilities. It's completely possible they just don't know yet how the hack occured, but they didn't answer the question to say "no, not log4j" so that's still on the table as a possibility. Whether or not it was log4j in this case, I'm going to guess that log4j will contribute to the rising tide of ransomware in the coming year.