chilly @chillyisheree

Good at everything, expert at nothing Everywhere Joined March 2019

Tweets

150
Followers

38
Following

138
Likes

1K

chilly @chillyisheree

2 months ago

@mn007vevo @BabulsArt The people seriously using DMA cards for research usually do that on lab machines, not the same gaming PC they run Valorant on. And Vanguard isn’t blocking ‘DMA cards’ in general – it’s going after spoofed drivers used to cheat.

0 0 0 26 0

View Details

chilly @chillyisheree

2 months ago

@mn007vevo @BabulsArt People are claiming permanent ‘Riot can brick your PC’ level damage – that’s what I replied to. Your Netflix camera analogy doesn’t match a purpose‑built DMA cheat card, and a recoverable reinstall/BIOS toggle is a soft failure, not a brick.

1 0 0 19 0

View Details

chilly @chillyisheree

2 months ago

@mn007vevo @BabulsArt A soft brick is, by definition, recoverable. That’s not the same as the ‘permanent, irreparable brick’ people are claiming. If reinstalling or toggling BIOS fixes it, calling it ‘bricked’ turns the word into a useless catch‑all.

1 0 0 20 0

View Details

chilly @chillyisheree

2 months ago

@mn007vevo @BabulsArt Brick isn’t a catch-all term. Soft brick still means recoverable, reinstall fixes it. My point was about the crowd claiming permanent, irreparable hardware damage. That’s not a soft brick, that’s a hard brick - and Vanguard isn’t doing that. We’re actually agreeing.

1 0 0 43 0

View Details

chilly @chillyisheree

2 months ago

@BabulsArt From my point of view a DMA card that can’t be used to cheat in their game anymore is basically a paperweight. That’s about usefulness, not literal permanent hardware damage – they’re just poking fun.

0 0 29 2K 0

View Details

chilly @chillyisheree

2 months ago

Worth clarifying: this isn’t ‘bricking’ hardware in the technical sense. The DMA cards themselves aren’t physically damaged - Vanguard is blocking the spoofed SATA/NVMe drivers/firmware they use to read game memory. That’s an access denial, not a dead device.

Riot Games @riotgames

2 months ago

congrats to the owners of a brand new $6k paperweight

2K 2K 36K 26.3M 6K

0 0 0 44 0

View Details

chilly @chillyisheree

2 months ago

@alan33633 @Jade_shitpost @riotgames No intern is writing kernel drivers at Riot. Since 2021, every kernel driver requires Microsoft’s own countersignature just to load on Windows, plus internal security review, legal review, and QA. An accidental bricking scenario also has zero confirmed cases.

0 0 0 55 0

View Details

chilly @chillyisheree

2 months ago

@Jade_shitpost @riotgames You typed that on a “corpo” device, through a “corpo” app, on a “corpo” network. The line you drew at Vanguard was never about principles. Have a good evening.

1 0 3 88 0

View Details

chilly @chillyisheree

2 months ago

@Jade_shitpost @riotgames You already gave this access to Microsoft, NVIDIA, and your antivirus. Vanguard isn’t unique in that sense. Also, kernel-level software operates under real law in every country Riot sells in. It’s not the wild west just because you don’t know the rules.

1 0 1 129 0

View Details

chilly @chillyisheree

2 months ago

@htgjiiihuu @riotgames It’s a cheat tool. Vanguard blocking its spoofed driver isn’t ‘bricking hardware’ - it’s blocking an attack vector. The card still works fine for what it’s legitimately supposed to do: nothing.

1 0 0 291 0

View Details

chilly @chillyisheree

2 months ago

@Jade_shitpost @riotgames Your logic is flawed. Kernel access defines capability, not behaviour. The driver is scoped to detection functions - there are no bricking routines because writing them would be a criminal act. “It could” isn’t evidence of “it did”.

2 0 1 378 0

View Details

chilly @chillyisheree

5 months ago

Valve’s current AC struggles, but they are playing a long-term game against hardware-based cheats. As DMA and kernel bypasses make client-side scanning less reliable, shifting the burden to server-side visibility culling and AI behavioral analysis becomes the only way.

0 0 0 40 0

View Details

chilly @chillyisheree

5 months ago

Yeah, Cheers Chrome.

0 0 0 36 0

View Details

chilly @chillyisheree

5 months ago

Its always fun to go back and watch youtubers / streamers react to the CS2 trailers. If only they knew what it was going to turn out like.

0 0 0 26 0

View Details

chilly @chillyisheree

5 months ago

@CounterStrike Stop teasing us with “Knife Sound adjustments” - Changing the gain and going home doesn’t count ☹️

0 0 4 2K 0

View Details

chilly @chillyisheree

6 months ago

It should now be safe to queue MM / Prem as Valve have reversed false bans and applied a fix.

CS2 @CounterStrike

6 months ago

Release Notes for today are up: store.steampowered.com/news/app/730/v…

352 86 2K 414K 63

0 0 0 139 0

View Details

chilly @chillyisheree

6 months ago

@SecurityTrybe Quoting for a floor standing rack.

0 0 0 63 0

View Details

chilly @chillyisheree

6 months ago

@DrexCS2 VAC bans and Game Bans are different on Steam: VAC is Valve Anti-Cheat, while “Banned by Game Developer” is a separate ban type that can still be automated. For CS2, Valve is also the developer so a CS2 Game Ban can be “from Valve” without being a VAC ban.

0 0 1 1K 0

View Details

chilly @chillyisheree

6 months ago

Everyone getting hit by possible false VAC bans likely has something in common. Shared software/driver feature that’s hooking into CS2 (overlay, capture, monitoring, RGB, input remap, GPU “enhancement,” etc.). This common factor could explain it. Nothing Confirmed by Valve.