Live data from Hacker News

I'm being cyberattacked by Tesla, Inc

dreamstation.systems

1–10 of 127 posts

Re: I'm being cyberattacked by Tesla, Inc

#4
In case of the very likely title only reader posting:

> Speculation: Assetnote pulled in everything it could find under tesla.com, including pool-ntp.tesla.com, which CNAMEs to pool.ntp.org, which can resolve to my machine — 67.215.249.229. The asset inventory saves this as a Tesla asset, and starts throwing exploits at me, a stranger.

> Not a vuln in Tesla, and I'm not asking for anything, but I just wanted to let you know that you may unintentionally be being a nuisance.

Re: I'm being cyberattacked by Tesla, Inc

#5

I would assume the fastest way to actually make this stop would be to setup a bunch of honeypot exploits, trigger their detection and someone will figure out what they did wrong. Other than not, with these huge companies you have 0 recourse.

(OOP here). I wonder if switching my replies from 299 to 200 OK would be enough for some of them.

Re: I'm being cyberattacked by Tesla, Inc

#8
> it has received ~8,000 requests from two of your scanning hosts

If it were 8000 requests per second, this might be worthy of some investigation.

But 8000 ntp requests alone consume far less than 1 us cent of compute + bandwidth. This isn't worth lifting a finger over.

Re: I'm being cyberattacked by Tesla, Inc

#9
post #5

I would assume the fastest way to actually make this stop would be to setup a bunch of honeypot exploits, trigger their detection and someone will figure out what they did wrong. Other than not, with these huge companies you have 0 recourse.

(OOP here). I wonder if switching my replies from 299 to 200 OK would be enough for some of them.

[deleted]

Re: I'm being cyberattacked by Tesla, Inc

#10

I would assume the fastest way to actually make this stop would be to setup a bunch of honeypot exploits, trigger their detection and someone will figure out what they did wrong. Other than not, with these huge companies you have 0 recourse.

I actually think this is brilliant. Let the scanner IP get access to the most unpatched Wordpress, maybe even generate some garbage ERP numbers.

Once the asset scanner detects the vulns, everyone will kick into high gear to patch this.

Post reply on HN