UPV + VetoPerf list several INJ signals as the main witnesses for these loud glitches: https://scientists.virgo-gw.eu/DataAnalysis/DetCharDev/users/narnaud/UPV/20250102/V1:Hrec_hoft_16384Hz/perf/vp.html.

• The top ten channels are

V1:SIB2_B2_DC, vetoed clusters: 157 (66.245 %)
V1:SIB2_RFC_PD1_DC, vetoed clusters: 151 (63.713 %)
V1:SIB2_RFC_QD2_H, vetoed clusters: 151 (63.713 %)
V1:ASC_B2_QD2_Sum, vetoed clusters: 151 (63.713 %)
V1:SIB2_RFC_PD2_DC, vetoed clusters: 150 (63.291 %)
V1:INJ_IMC_TRA_DC, vetoed clusters: 149 (62.869 %)
V1:INJ_ITF_INPUT, vetoed clusters: 149 (62.869 %)
V1:INJ_IBJM_DC_H, vetoed clusters: 142 (59.916 %)
V1:BsX_QN_DC, vetoed clusters: 142 (59.916 %)
V1:INJ_IBJM_DC_H_e, vetoed clusters: 142 (59.916 %)

An example before / after, using the channel V1:SIB2_B2_DC as a veto for those glitches.

These loud glitches are likely to impact the quality of the Virgo Science data and may prevent using them in case of a low-latency trigger.