Urgent.News

What's breaking now, across thousands of outlets.

Tech

I'm being cyberattacked by Tesla, Inc

Article URL: https://dreamstation.systems/personal/tesla.html Comments URL: https://news.ycombinator.com/item?id=49686766 Points: 166 # Comments: 40

Tesla Inc. is experiencing an unusual cyberattack, with persistent traffic coming from three specific IP addresses. The traffic originates from three scanners: 54.165.75.96, 35.168.63.24, and 52.44.200.251. All of these IPs are associated with Amazon Web Services (AWS). The attack surface management tool, now called Searchlight Cyber, is using continuous threat exposure scanners for automated checks on customers' assets.

Assetnote mistakenly identifies the reporter's server as an internal Tesla asset due to the use of pool-ntp.tesla.com, a CNAME to pool.ntp.org. The NTP Pool is a round-robin of volunteer NTP servers that the reporter is part of, and the asset discovery mistakenly includes every IP that pool-ntp.tesla.com can resolve. The reporter has contacted Tesla about the issue but has not received a response.

The attacks have included various exploits like path traversal, webshell uploads, probing software internals, SSRF, Log4Shell, and more, with over 50,000 requests from Assetnote hosts since August 21. The reporter has observed that Tesla's scan is targeting every IP that pool-ntp.tesla.com can resolve, causing unnecessary traffic on the reporter's server.

Written by urgent.news from Hacker News Best's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at dreamstation.systems →

More in Tech

Mainframe Migration Tools: What Works and What Fails

Every mainframe migration begins with someone searching for mainframe migration tools, and every vendor demonstration that follows looks remarkably convincing.

  • Discovery and analysis tools are most valuable for understanding complex mainframe environments.
  • Rehosting platforms are predictable but don't address COBOL codebase maintenance.

My verifier accepted "13 of 13" by finding the number 13 once

Claims in my project are written as a pair: some count out of some total, each side backed by a cell in a generated table. A checker resolves the claim by finding the evidence for both numbers.

  • Checker resolved 13/13 by finding a single cell with number 13
  • Split pairs now require resolution over two distinct cells
  • Carried tables must either count or be declared out of scope explicitly

More from Sunday 13 September →