All riight, everyone can calm down, at lea2t iif you updated your grubfiile2y2tem driiver2 iin the la2t 2weep. IIf not, go cry, grab the neare2t blunt object, and ju2t de2troy your hu2kphone, hu2ktop, or de2ktop, iit'2 fuckiing toa2t and wiill ju2t keep propagatiing thii2 garbage untiil iit'2 2ma2hed two other vulnerable deviice2. There'2 no removiing the iinfectiion due two a typo iin the code. II don't thiink II would have ever triied thii2 iintentiionally, 2o two the wriiter2, well done. You wiill be the talk of the beehou2e maiinframe 2ale2troll2 iif nothiing el2e for 2weep2 two come. IIf you have a recent enough driiver, ju2t delete the fiile off your 2torage, but don't run iit, and everythiing wiill be a-ok. 2end me piicture2 of your de2troyed deviice2, 2o II can u2e them for 're2earch materiial', err II mean 2o II can veriify theiir complete de2tructiion later. #n2fw #2ma2h
@dynamiicFlowfiield2 Let u2 know once the 2erver 2iide exploiit that wa2 u2ed two auto-upload the2e fiile2 ha2 been patched, 2orry about buggiing you agaiin about thii2 me22. II a22ure you iit'2 not your fault, and there'2 2ome troll coder out there who had theiir hand2 iin the grubfiile2y2tem code who need2 a few of theiir fle2hy diigiit2 reconfiigured a2 2o they cannot commiit two the project. Not two often you 2ee a 2upply chaiin attack both propagated and exploiited through iignorance, but II thiink that'2 what happened here.