News for hackers. Stuff that matters.
Re:GNU/Linux local username triggers Steam VAC ban by ajross on Monday January 01, 2018 @01:27PM (#16047245)
So in one sentence, a user name containing "catbot" is a legitimate signature of an actual work of malware Valve is trying to mitigate.

HN, you got trolled. There's nothing wrong here at all.

Re:GNU/Linux local username triggers Steam VAC ban by vladd on Monday January 01, 2018 @02:26PM (#16047559)
A "legitimate" signature (or, for a better word, a good-performing signature) is one that performs well on both precision and recall ( https://en.wikipedia.org/wiki/Precision_and_recall ).

Precision is the ratio between correctly-identified cheaters and the total number of people matched by the signature.

Recall is the ratio between correctly-identified cheaters and the total number of cheaters in the system.

In this case, the signature had good recall but poor precision, as those threads describe cases that make it plausible to have a "catbot*" username without cheating.

(I said "had" because the recall rate is going to drop when the string gets changed by the cheat authors. So long-term, the signature is poor on both recall and precision.)

The most problematic issue I see for Valve is not the lack of measurement of precision and recall for their VAC ban signatures, but rather the inability to obsess over their customer experience and react properly when relevant issues in their products are reported.

Re:GNU/Linux local username triggers Steam VAC ban by rahimnathwani on Monday January 01, 2018 @03:14PM (#16047794)
"poor precision"

How so? Of Steam's users that are running linux and have 'catbot' as part of a username on their system, what proportion do you think are running a cheat bot? 99%? 99.9%?

What level of precision would you say it not 'poor precision'? 99.999%?

Re:GNU/Linux local username triggers Steam VAC ban by Kr4ken on Monday January 01, 2018 @03:47PM (#16047965)
None anymore, the cheaters have already stopped using catbot as their usernames. https://github.com/nullifiedcat/catbot-setup/commit/c2d22ee9.... This is further proof of how poor of a response this was by Valve.
Re:GNU/Linux local username triggers Steam VAC ban by paulmd on Monday January 01, 2018 @06:04PM (#16048551)
That changes nothing. Every single anti-cheat mechanism will eventually be identified and worked around, it's a continuous game of cat and mouse. This is why bans are delayed and specific reasons are rarely given, to prevent identification of the specific mechanisms used.

It's like treating a disease with antibiotics, eventually the disease builds a tolerance and you need to find a new drug. By using multiple drugs you can hopefully kill it before it can resist any given drug, but in practice tolerance builds regardless of your best efforts.

These cheats are actually big business nowadays, people have a financial incentive to work around them as quickly as possible.

Re:GNU/Linux local username triggers Steam VAC ban by user5994461 on Monday January 01, 2018 @08:16PM (#16049097)
You're wasting your time arguing. The poster you are replying to is affiliated with the bot.
Re:GNU/Linux local username triggers Steam VAC ban by paulmd on Tuesday January 02, 2018 @12:01AM (#16049980)
Haha, good catch, he commented on the issue in the OP. We are definitely getting trolled here.

https://github.com/Kr4ken-9/cathook

Golly, hack authors are just so concerned for the well-being of random internet strangers, how dare you doubt their sincerity! /s

Re:GNU/Linux local username triggers Steam VAC ban by Kr4ken on Monday January 01, 2018 @07:39PM (#16048953)
I don't know any other anti-cheat that has used a blacklisted username as a mechanism. Valve did not bother to obscure any part of this mechanism, they publicly confirmed that this mechanism was banning people due to their name. This is an open source cheat that has not generated any revenue, and it was worked around as soon as it was identified. Regardless, saying that this changes nothing is ridiculous, this mechanism was aimed mostly at cheaters, with some innocent in the crosshairs. Now, all cheaters have worked around this and only innocent are left in the crosshairs.
Re:GNU/Linux local username triggers Steam VAC ban by rahimnathwani on Monday January 01, 2018 @03:56PM (#16048001)
I was responding to a comment made when "the signature had good recall".

So whilst you have a reasonable point, it's not relevant to the point I was making, which is that the precision of the rule (after implementation, and before discovery) probably exceeded 4 nines, which doesn't seem like 'poor precision' to me, without further detail on the requirements.

And BTW I have no opinion about whether this was a good or bad move by Valve. I don't have sufficient context for that, and my comment was intentionally focused to try and understand what the person to whom I replied thought would be acceptable precision.

Re:GNU/Linux local username triggers Steam VAC ban by geofft on Monday January 01, 2018 @06:00PM (#16048540)
> those threads describe cases that make it plausible to have a "catbot" username without cheating.*

Plausible or possible? All heuristics have potential false positives (e.g. maybe someone puts the actual catbot binary in the blockchain, and now all Bitcoin users get banned??). I don't see any evidence in the GitHub thread of someone accidentally hit by this. And I see evidence of one person legitimately being hit by this (someone claiming that they are running the bot, just not with the same Steam account).

So I think this heuristic is working properly. (Whether to allow any theoretical risk of a false positive is another discussion, but, Valve is a business, it seems totally reasonable to me for them to risk it.)

Re:GNU/Linux local username triggers Steam VAC ban by janoc on Monday January 01, 2018 @02:22PM (#16047533)
The problem is that everything is wrong here. Username is not a signature of malware by itself. There could be a ton of reasons why someone could have an account like that on the machine - be it someone's name, maybe some AI project, perhaps a robotic feline, who knows.

Unfortunately, it seems that Valve's software doesn't bother to actually check whether the machine has any malware installed, it bans anyone who has any account on the machine that matches a regexp. Innocent or not, who cares, right?

How "effective" this approach is is very much documented by the fact that as soon as the botters caught wind of this they have changed the username they use and Valve can play a game of cat & mouse with them now.

It is not the first time Valve got caught by doing dumb/lazy stuff like this. E.g. Steam was known to erase your entire machine (or at least what your current user had access to - so most likely all you data) because of lazy programming and hardwired assumptions (see here: https://www.theregister.co.uk/2015/01/17/scary_code_of_the_w... ). Their response has been pretty similar too - "Works as intended, go away, we don't care".

Yay ...

Re:GNU/Linux local username triggers Steam VAC ban by paulmd on Monday January 01, 2018 @05:42PM (#16048451)
> Username is not a signature of malware by itself

Devoid of all context, no it's not. When a malware is known to exclusively use a particular and uncommon pattern, yes it is.

If you remove all context then nothing is ever a signature of malware. Maybe there is a legitimate reason for a third-party program to be writing your memory or injecting DLLs, you never know! But in practice those are red-alert triggers for any anti-cheat.

Re:GNU/Linux local username triggers Steam VAC ban by rnhmjoj on Monday January 01, 2018 @01:41PM (#16047325)
A legitimate signature would be a sequence of actions the client sends the server that are clearly not possible to have been performed by an actual user playing the game. Like an incredibly improbable statistic or too fast actions or something else.

This is a poor solution: it's the equivalent of blocking spammers by IP address. It works but will also lock out legitimate users.

Re:GNU/Linux local username triggers Steam VAC ban by ajross on Monday January 01, 2018 @01:49PM (#16047366)
That's not the way this kind of thing works, not even in commercial AV. What you are asking for is for Valve to solve the halting problem before addressing ongoing actual cheating in it's games. That's ridiculous.

You take what clues you can get and you push the fix. This is what all their users not named catbot want.

Re:GNU/Linux local username triggers Steam VAC ban by revelation on Monday January 01, 2018 @02:03PM (#16047445)
Which is why commercial AV routinely throws up entirely bogus reports. Not a good example.

Comparing statistics (accuracy, reaction time, chat messages, what have you) server-side to a not cheating player population seems like a very promising solution, given it doesn't involve the game client (which is assumed compromised). I don't see how that has anything to do with the halting problem.

Re:GNU/Linux local username triggers Steam VAC ban by jimrandomh on Monday January 01, 2018 @01:50PM (#16047373)
This particular detection seems very unlikely to ever have a false positive. The noise about false positives appears to be coming from the authors of the cheat software themselves.
Re:GNU/Linux local username triggers Steam VAC ban by lakechfoma on Monday January 01, 2018 @02:25PM (#16047557)
It's not about false positives, it's about the half ass solution. The name is just gonna change and it'll be an impossible cat and mouse game
Re:GNU/Linux local username triggers Steam VAC ban by rnhmjoj on Monday January 01, 2018 @02:39PM (#16047630)
They have already implemented randomly generated names: https://github.com/nullifiedcat/catbot-setup/pull/11/files
Re:GNU/Linux local username triggers Steam VAC ban by throwaway2048 on Monday January 01, 2018 @03:24PM (#16047842)
all anti-cheat is fundamentally cat an mouse, when you can control the kernel (applies to both linux and windows) you can lie about anything anticheat tries to detect.

There is no bulletproof solutions.

Re:GNU/Linux local username triggers Steam VAC ban by lakechfoma on Monday January 01, 2018 @03:28PM (#16047859)
You're right but some statistics analysis on the gameplay by players would do a lot more to reveal bots than analyzing usernames, especially once the bots start using random diceware names
Re:GNU/Linux local username triggers Steam VAC ban by throwaway2048 on Monday January 01, 2018 @06:07PM (#16048560)
I'm guessing this is how they determined this was a valid metric, everybody with a catbot user statistically looked like a hacker, and nobody didn't look like a hacker.
Re:GNU/Linux local username triggers Steam VAC ban by paulmd on Monday January 01, 2018 @05:46PM (#16048465)
They do that too, but this was an easy 'tell' for a while.
[dead]
Re:GNU/Linux local username triggers Steam VAC ban by anonymousab on Monday January 01, 2018 @02:36PM (#16047616)
'catbot' is a name I can certainly see being used by for a PC username on a gamer's system.

It's certainly not unique if you google around. I don't have steam locally so I can't use their username search to check for similar ones.

Re:GNU/Linux local username triggers Steam VAC ban by Moter8 on Monday January 01, 2018 @04:35PM (#16048176)
A search gives me 739 results, some appear to be just "duplicate" though.

There are 8+ accounts which seem real on the first two pages, so there must be false positives as you implied.

http://steamcommunity.com/search/users/?text=catbot&x=0&y=0

[dead]
Re:GNU/Linux local username triggers Steam VAC ban by Moter8 on Monday January 01, 2018 @04:36PM (#16048182)
You can express most of what you said in normal, clear words, without having to insult the other person.
Re:GNU/Linux local username triggers Steam VAC ban by subway on Monday January 01, 2018 @01:51PM (#16047383)
By that same token, use of sudo is a legitimate signature of the malware.

That said, its a really shitty signature with lots of false positives -- catbot is exactly the sort of strange names I assign to hosts or projects.

Re:GNU/Linux local username triggers Steam VAC ban by userbinator on Monday January 01, 2018 @01:57PM (#16047410)
catbot is exactly the sort of strange names I assign to hosts or projects.

...and also doesn't look too out-of-place as a gamer handle --- in other games I've seen players with variants of 'cat' and 'bot' in their names (catman, botman, catfish, fishbottom, etc.), which didn't seem to be cheating either.

If it was a name with more "entropy", like jH3bzKflAC5, then the case for it being a signature might be far clearer.

Re:GNU/Linux local username triggers Steam VAC ban by FRex on Monday January 01, 2018 @02:45PM (#16047657)
It's about the local Linux account name (which frankly Steam has no business touching or inspecting the contents of past pasting it into a path IMO), not the in chosen steam name (which can be anything) nor the unique steam name in profile link (which I think comes from the login, I'm not sure now).

In any case - both are all over the place and in online games there are often crazy names that look like the came from /dev/random. It'll also be easily circumvented now that it has been discovered and it was dumb in the first place.

Valve really dropped a ball, it's not like they don't know how crazy, meme fulled or troll-y usernames get on their platform.

Outright VAC ban (that's a big deal) for something like that is absolutely idiotic (extra inspection that doesn't affect anything for legitimate users - sure).

Re:GNU/Linux local username triggers Steam VAC ban by Zpalmtree on Monday January 01, 2018 @11:32PM (#16049886)
Unique steam urls' have to be manually set and don't exist by default.
Re:GNU/Linux local username triggers Steam VAC ban by throwaway2048 on Monday January 01, 2018 @06:12PM (#16048588)
Valve can easily query who has the usernames catbot, and then correlate it with hack like activity, and draw the conclusion that false positives aren't an issue in the real world.

After all the banwave only hits once.

Re:GNU/Linux local username triggers Steam VAC ban by lakechfoma on Monday January 01, 2018 @02:25PM (#16047549)
The interesting thing is that this "legitimate signature" will just change. Maybe to another basic name, maybe a random string, maybe diceware. No one is trolled.
Re:GNU/Linux local username triggers Steam VAC ban by stordoff on Monday January 01, 2018 @02:29PM (#16047574)
I wouldn't be surprised if it starts using real names to avoid this particular detection - gather a few thousand real Steam usernames, and create variants of them at runtime.
Re:GNU/Linux local username triggers Steam VAC ban by nitrogen on Monday January 01, 2018 @02:33PM (#16047592)
Aimbots ruined TF2 for me a couple years ago. One of the things they used to do to make them harder to kick/ban was change their name to the name of a different real player on the server every second.

The mentality that drives the use of aimbots is a disgusting scourge on humanity.

Re:GNU/Linux local username triggers Steam VAC ban by Moter8 on Monday January 01, 2018 @04:38PM (#16048189)
But they player/Steam ID stays the same if you look via the console, iirc it was `status`?
Re:GNU/Linux local username triggers Steam VAC ban by paulmd on Monday January 01, 2018 @05:49PM (#16048475)
One of the mechanisms to avoid a server ban (different from a VAC ban) is to rapidly switch between names of other players on the server (but with unprintable/non-breaking characters added). You need to use 'status' to tell them apart.
Re:GNU/Linux local username triggers Steam VAC ban by gaius on Monday January 01, 2018 @02:23PM (#16047538)
Tell me, have you ever been to Scunthorpe?
Re:GNU/Linux local username triggers Steam VAC ban by tzs on Monday January 01, 2018 @03:29PM (#16047865)
That reminds me of Everquest and "cock".

Their chat filters did not allow the string "cock" in chat...and then they put a bunch of nasty cockatrices in the Dreadlands and in the Overthere, along with quests that asked you to seek out their eggs, feathers, and beaks, thus giving you a reason to use the string "cock" when talking with others.

Re:GNU/Linux local username triggers Steam VAC ban by Sir_Substance on Monday January 01, 2018 @02:33PM (#16047597)
> So in one sentence, a user name containing "catbot" is a legitimate signature of an actual work of malware Valve is trying to mitigate.

I think signature is a strong word. This is kind of like comparing the color of the ink used to sign for something and ignoring the actual signature.

Re:GNU/Linux local username triggers Steam VAC ban by shawnz on Monday January 01, 2018 @02:57PM (#16047706)
> a user name containing "catbot" is a legitimate signature of an actual work of malware Valve is trying to mitigate.

Who suggested otherwise?

Re:GNU/Linux local username triggers Steam VAC ban by paulmd on Monday January 01, 2018 @05:53PM (#16048499)
> Who suggested otherwise?

A dozen or so people in this thread?

Re:GNU/Linux local username triggers Steam VAC ban by mabbo on Monday January 01, 2018 @04:09PM (#16048049)
Who the heck is valve to say what usernames I can and cannot have on my system? I don't even play TF2.

What happens if the cheaters decide the change the 'triggering' username to something far more common? Guest, admin, local, user, etc. Now valve is allowed to ban everyone who has that username on their system?

Re:GNU/Linux local username triggers Steam VAC ban by dang on Monday January 01, 2018 @05:37PM (#16048427)
> HN, you got trolled.

HN is as much your comment as any other.

Re:GNU/Linux local username triggers Steam VAC ban by paulmd on Tuesday January 02, 2018 @12:08AM (#16050009)
No, the hack authors who filed the pull request are actually posting here in this thread.

eg this guy: https://github.com/Kr4ken-9/cathook is kr4ken on HN, there's probably others here who are smart enough not to link their black-hat identity with HN.

This is literally blackhats bitching that they got VAC-banned, 100% legitimately, and then concern-trolling us about what-if scenarios about some hypothetical innocent user who might have been swept up with their script-kiddie customers.

Can't say that such opinions really have any place here, IMO, considering that they are the ones who created the problem in the first place. Maybe it's not worth shutting them down, but they certainly shouldn't be celebrated or legitimized in any fashion.

Scorn is an entirely appropriate community reaction here, and a mod tipping the scale in favor of black-hats is not really appropriate IMO.

Re:GNU/Linux local username triggers Steam VAC ban by dang on Tuesday January 02, 2018 @11:03AM (#16052618)
I wasn't talking about that and am not taking any kind of side. If you think there's abuse going on, emailing [email protected] is the thing to do, and then we can take a closer look.

My point is the orthogonal one that it's incongruent to snarkily diss HN when you're as much a part of the community as anyone else is. It makes no more sense to say "HN got trolled" than "HN debunked getting trolled". People don't do this to be informative, but rather to superciliously position themselves above others. That degrades the spirit of the community here, which is already so fragile. That's why I reply to such comments the way I did.

Re:GNU/Linux local username triggers Steam VAC ban by hitekker on Tuesday January 02, 2018 @12:14PM (#16053298)
We may each be a part of HN but that doesn't mean we can't criticize what we perceive to be the gestalt of HN.

It's like saying "<Insert Community / Country / Organization Name>, goddammit!"

I personally don't mean that I'm better than everyone in said community, but that I'm disappointed with the prevailing sentiment, and so feel the need to signal my separation on the issue.

It's shorthand "I don't identify with <Community> on <Issue X>".

People do indeed abuse this rhetoric to feel superior to others, e.g., "Reddit is a hivemind!". But on issues where the community clearly falls prey to its biases, a little snark now should remind us to avoid those collective pitfalls in the future.

Re:GNU/Linux local username triggers Steam VAC ban by hitekker on Tuesday January 02, 2018 @01:00AM (#16050171)
I agree. Implying that HN users aren't generally susceptible to blackhat trolling is naive.

Our community has its strengths but some subjects like politics provoke a suspension of critical thinking. In this case, small time hackers being punished by a big company in a seemingly overkill way for a seemingly innocuous slight.

Ideally, a moderator should be aware of the biases of the community and adjust the discussion accordingly. Or at least when the lies being perpetrated are as obvious as it is in this thread.

Re:GNU/Linux local username triggers Steam VAC ban by hitekker on Monday January 01, 2018 @04:34PM (#16048175)
More like "HN, you got triggered".

Anecdotally, the people who screech about and around VAC bans are the same people who will ruin online games with botting, scripting or just general douchebaggery.

Basically, no one notices VAC if they aren't trying to screw over other gamers.

Those who do so so repeatedly, often resort to comment threads like this one, venting vitriol on the off-chance the more-gullible will confuse it as signals of a larger problem.

Steam has many issues: poor customer service, a wash of bad content, a lack of focus on making games.

But being too hard on those poor, upstanding cheaters? Not an issue.

Re:GNU/Linux local username triggers Steam VAC ban by FRex on Monday January 01, 2018 @02:34PM (#16047600)
Then perhaps I should make a fork that uses your username to get you banned and then proceed spit in your face when it happens and tell you it's your fault.

Or reinstall my TF2 and get banned so then I can tell you to stick it.

It's VAC that's doing the trolling here. Person's OS (not even Steam) username is not a cheat (and Steam frankly has 0 reason to examine its name in any way for any purpose, for installing games just pasting will do and for everything else there is a Steam username).

This is bullshit, will be defeated now instantly that it came out and on the level of dumb antiviruses that delete exes (i.e. my compiled Pascal and C++ programs) and claim the reason was "unknown low spread program" (yes, that happened, because clearly, unknown program = virus).

VAC has sainthood status now, Valve social media staff often tells people it's 100% foolproof and bans are never appealed, people who claim they were unfairly banned are shitted on by the community and it's undisputable (although there were overturns i.e. when CoD players got banned by Steam's mistake[0]) but they do crap like that?

It's like Destiny 2 bans last year, they were all "hand made by staff and 100% confirmed cheaters" and then a couple hundred got overturned and claimed to be "software error".

What next? Banning everyone who has a GitHub account or knows git because the aimbot code is hosted on GitHub? Banning people from sites for having HN accounts because it's a "hackers" site?

What planet do people like you come from?

[0] - https://kotaku.com/5597038/valve-bans-modern-warfare-players...