Usually end up digging through scripts looking for their payload or something similar. Defenitely not gotten to the point I'm actively working on a mechanism to

Usually end up digging through scripts looking for their payload or something similar. Defenitely not gotten to the point I'm actively working on a mechanism to fingerprint fingerprinters, but give it time. I'm on an embedded/graphics shtick at the moment, and once it gets feeling old enough, I may actually try doing a deep dive on neutering the thing. Unfortunately, it's held up by the fact I'm a stickler for consistency of action, and I've yet to come up with a rationalization that justifies fingerprinting fingerprinters without lending an extra chip of credence to their own misbehavior. Golden Rule implies treat others ss they treat others, but eh... That starts writing a blank check for people to ruin things for everyone else in a race to the bottom. However: A) Heavy use is made of shifting data into relatively unused parts of Unicode via bitshifts. You could make something that picks that up and uses that as a heuristic. B) Large base64 encoded chunks followed by XORs are also prevalent. C) The bloody thing touches every imaginable web browser API call. You'll probably filter out tons of other "defensively obfuscated javascript" by filtering on these behaviors, but over time, I've come to realize that if someone shows so little consideration for what they are doing to my power consumption by cramming down gobs of shite for my processor to slog through, I really can't build up the motivation to do business with them. I have a computer where bloated as hell websites run like they did in the 90's/00's all because somebody wants to slide something under the radar. No thanks.