Abuse report: ongoing unauthorised access from 78.17.132.67 (516116.vm.spacecore.network)

We operate tooldirectory.ai. A server on your network has been used for sustained unauthorised access to our production systems since 16 November 2026, and the activity is still going on. We did not authorise any security testing.

Source

  • IP address: 78.17.132.67
  • Reverse DNS: 516116.vm.spacecore.network
  • Network: 78.17.132.0/23, AS198037

Targets (HTTPS, port 443)

What happened (all times UTC)

  • 2026-11-16, 02:37 to 21:54: 44 throwaway accounts were registered on our API (usernames such as qa_probe_1364, ssrfprobe2157, secscan3119) and used to write more than 200 unauthorised records and 81 files into our production database.
  • Those records carried script-injection payloads and addresses aimed at internal and cloud-metadata services (169.254.169.254, 127.0.0.1, metadata.google.internal).
  • 2026-11-17, 02:23:31: the same tool returned and registered another account (qa_probe_6657).

Evidence linking this to your address

The attacker embedded six webhook.site capture addresses in the records written to our database. webhook.site records the address that created each one. All six were created by 78.17.132.67 with the user agent curl/7.88.1, each less than two minutes before the matching record appeared in our database. The same address then requested them 12 more times.

webhook.site tokenCreated by 78.17.132.67First written to our database
cd5323e9-6bac-432b-b3f5-9148e0f7a2412026-11-16 04:50:222026-11-16 04:50:51
1e40b242-7c78-48e6-b2f9-2d5c097b8f022026-11-16 08:28:322026-11-16 08:30:30
0d85d2c1-3509-4953-8ceb-e76c03fc88ab2026-11-16 08:29:502026-11-16 08:30:34
3c658b04-8731-41df-bbde-31412745f5412026-11-16 08:34:012026-11-16 08:34:19
abf3f502-abc6-42b6-8e8f-bd0102eed1732026-11-16 08:37:092026-11-16 08:37:15
96075151-3fe1-4593-821a-165dae222fda2026-11-16 08:48:552026-11-16 08:49:34

You can verify each one yourself until 23 November 2026, when they expire: request webhook.site/token/ followed by the token and read the ip and created_at fields. We have saved copies.

Our API host does not record client addresses, so we cannot send request logs that show your IP directly. Your own traffic records for this server towards the targets above, in the time windows above, should confirm it.