I'm being cyberattacked by Tesla, Inc

fred_is_fred

I'd report this to AWS instead since Tesla doesn't seem aware. It's AWS IPs as the source.

richwater

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.

tekla

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.

walrus01

Remember in 2003 when netgear hardcoded a university's NTP server into a ton of their products? Well.... https://www.google.com/search?&q=university+ntp+server+netge... https://pages.cs.wisc.edu/~plonka/netgear-sntp/

VladVladikoff

> rg -zFI pool-ntp.tesla.com access.log* Neat! Didn’t know about this command that’s very helpful

londons_explore

> 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.

NotWhatUThink

> They tried all kinds of exploits against me ... probing WordPress and other CMS management endpoints This is standard bot crawler traffic. Anyone who runs a home server sees attempts to load wp paths all the time

simonjgreen

I’m pretty sure this way they’ve hardcoded the NTPs is actually against the ToS for use of the NTP pool too. The way a vendor embedding NTP is _meant_ to do so is documented here: https://www.ntppool.org/en/vendors.html On another note, back when I ran a web hosting business we hosted a few NTP servers in the pool. It’s such a simple thing to give back, and worth anyone who can make a stable contribution doing so.

buzer

CNAME'ing pool-ntp.tesla.com to something they do not control is already quite risky as it would allow someone to e.g. request pool-ntp.tesla.com certificate though it might take quite a few tries.

graypegg

Thankfully it doesn't seem to be much traffic, but still... weird. You'd hope at somepoint the weird responses would get looked at in some log, but I won't hold my breath for that haha. Tangential, but I love the design of your blog. That's so freakishly accurate to old GNOME 2 Ubuntu, amazing work.

andai

I really like this website's theme. I noticed this yesterday when using a very old iOS version: Shiny UI is morale-boosting.

sippingabonedry

This seems like a gross exaggeration. This happens EVERY day to EVERY web server out there. I have a personal site that gets thousands of requests per day from bots. Running a public server (like NTP) means you will get tons of strange requests. Moreso if you run a web server on the same IP because bots will scrape certificate transparency logs. The entire IPv4 space is scanned continuously. This may sound harsh, but you cannot stop it. It is whack-a-mole. Filter it and move on, go outside and touch grass, seriously. This is not worth being upset over. I treat these as an opportunity to tune my filters and firewall rules.

consensus1

Is this basically a free pen test, or am I misunderstanding the setup?

darwinlee

“You must absolutely not use the default pool.ntp.org zone names as the default configuration in your application or appliance.” ref: https://www.ntppool.org/en/vendors.html

caaqil

Huh, are we sure this is just NTP shenanigans and not some super duper dangerous AI agents "escaping" the "containment"?

matt3210

I bet we'll find that its openAI agent benchmarks off on their own again

motbus3

Do a Tesla move and say that's a new service and they need to pay 10000 a month to keep using the service otherwise you reserve the right to mess up with the responses. :P of course, just a joke, but that's what they do

KaiserPro

Tangential; I love the style drop down.

iancarroll

As a bug bounty researcher, my systems would do the same thing if they ended up georouted to this IP. *.tesla.com is marked as in scope on https://bugcrowd.com/engagements/tesla , and my agents will probe anything under there as it is presumed to have explicit authorization. Not sure if there is a great solution, but I'm inclined to say that attack traffic like this is the new normal. In fact, the attack volume they got is quite small compared to the volume I have seen on other tech company subdomains - the new normal is probably much worse.

larodi

So many of the news on HN, such as present one, can be actual stories/scenes from a cyberpunk game/movie these days, that we can safely assume this (otherwise imaginary) future has already arrived.