← Back to context Comment by croes 6 months ago It‘s not a C&C/Botnet 15 comments croes Reply cuu508 6 months ago It is C&C -- it instructs their site visitors to DOS a specific site. zahlman 6 months ago By this logic, all malicious JavaScript (obvious example is cryptominers I guess, assuming no JS sandbox escape) is C&C, yeah? As it "instructs site visitors" to do something harmful locally? croes 6 months ago A C&C controls a botnet, where is the botnet? cuu508 6 months ago The browsers of their site visitors. 11 replies →
cuu508 6 months ago It is C&C -- it instructs their site visitors to DOS a specific site. zahlman 6 months ago By this logic, all malicious JavaScript (obvious example is cryptominers I guess, assuming no JS sandbox escape) is C&C, yeah? As it "instructs site visitors" to do something harmful locally? croes 6 months ago A C&C controls a botnet, where is the botnet? cuu508 6 months ago The browsers of their site visitors. 11 replies →
zahlman 6 months ago By this logic, all malicious JavaScript (obvious example is cryptominers I guess, assuming no JS sandbox escape) is C&C, yeah? As it "instructs site visitors" to do something harmful locally?
croes 6 months ago A C&C controls a botnet, where is the botnet? cuu508 6 months ago The browsers of their site visitors. 11 replies →
It is C&C -- it instructs their site visitors to DOS a specific site.
By this logic, all malicious JavaScript (obvious example is cryptominers I guess, assuming no JS sandbox escape) is C&C, yeah? As it "instructs site visitors" to do something harmful locally?
A C&C controls a botnet, where is the botnet?
The browsers of their site visitors.
11 replies →