[Spy Nodes && S2X] Attack on the Network in Progress

Meuh6879

legendary

Activity: 1512

Merit: 1012

Update of my follow up. Wink

Code:

100.35.27.249
104.128.94.12
104.155.122.212
106.111.74.47
106.117.151.89
106.186.31.140
106.200.239.231
106.75.146.143
109.105.160.122
109.174.112.250
109.225.25.187
109.225.28.228
109.254.84.135
109.94.2.1
111.178.9.81
115.132.248.36
115.219.169.242
118.93.103.208
121.86.50.33
128.70.191.84
128.8.124.7
129.13.252.36
129.13.252.47
13.230.150.193
134.255.136.170
136.243.139.120
136.243.139.96
142.105.252.237
144.217.10.217
145.132.191.135
146.120.56.238
146.60.38.249
151.225.139.222
159.224.90.59
162.250.221.238
170.79.45.59
171.8.110.21
173.212.193.11
173.245.203.184
173.255.251.118
174.34.172.203
176.104.14.35
176.215.228.52
176.36.32.34
178.255.153.166
180.111.132.131
181.59.126.46
182.244.235.86
183.204.68.26
184.207.138.127
184.98.248.101
185.57.28.103
185.59.58.157
187.221.99.132
187.65.144.146
187.75.50.120
188.134.77.121
188.163.74.12
188.192.250.36
188.234.228.62
188.37.67.242
188.65.213.21
195.91.160.170
198.199.89.131
198.48.223.50

200.0.51.232
200.114.199.78
2001:0:5ef5:79fb:147c:1e50:6b00:9ebf
202.108.211.56
203.220.88.53
203.3.109.194
205.251.22.236
212.108.43.57
212.159.113.138
213.220.247.85
213.55.211.9
216.19.183.58
217.208.126.75
217.61.217.125
218.226.212.4
218.87.96.161
220.162.105.211
222.180.100.198
222.180.63.74
222.215.172.99
222.93.10.16

24.119.224.62
24.175.192.11
24.18.147.55
2607:5300:60:1bd1::1
2a00:1398:4:2a00::a1
2a00:1398:4:2a00::a5
2a03:b0c0:3:d0::5c9:4001

31.130.95.253
31.223.227.198
31.36.66.102
35.165.221.21
35.187.187.248
35.189.230.22
35.196.249.50
35.196.46.145
36.151.8.238
37.113.142.45
37.113.27.238
37.135.34.116
37.15.117.117
37.201.240.133
37.229.201.178
37.24.148.38

45.33.65.130
46.101.246.115
46.229.147.14
46.246.154.92
46.246.49.79
46.53.195.62
47.104.84.114
47.223.222.114
47.254.128.169
47.89.246.242
47.89.252.244
47.90.4.203
47.93.23.68
49.84.247.96

5.1.55.184
5.165.16.34
5.3.242.107
5.44.168.103
50.66.58.222
58.108.89.24
59.110.63.71

60.175.104.134
62.32.1.225
62.47.222.32
62.80.189.158
62.87.203.34
64.228.213.224
67.52.230.18
69.84.31.75

70.30.104.212
70.33.168.20
70.33.168.27
71.11.106.234
71.70.195.177
71.84.104.6
72.192.93.35
72.36.89.11
73.114.228.205
73.222.196.104
73.236.191.56
74.102.109.216
74.132.27.118
74.207.240.152
76.254.56.180
77.247.181.162
77.50.100.120
78.106.11.204
78.146.56.214
78.46.79.17
78.99.22.173
79.132.116.135
79.169.200.81
79.73.36.52

80.100.203.151
81.111.144.79
81.16.165.228
81.171.56.134
82.130.103.18
83.161.249.125
83.169.228.178
83.243.39.142
84.23.44.69
84.23.59.175
84.242.74.251
84.29.73.246
87.120.1.28
87.213.253.167
87.214.171.55
87.3.86.99
89.114.207.82

90.94.191.16
91.106.149.46
91.202.132.248
91.78.240.152
93.202.6.16
93.219.134.103
93.75.30.249
94.100.213.84
94.103.228.161
94.25.171.139
95.246.207.1
95.27.87.58
95.29.41.93
95.90.243.59
96.227.219.182
96.81.220.85
98.221.120.90
99.41.87.194

Matched IPs between G. Maxwell & Me :

Code:

128.8.124.7
129.13.252.36
129.13.252.47
136.243.139.120
188.65.213.21
205.251.22.236
35.196.46.145
45.33.65.130
59.110.63.71
72.36.89.11
82.130.103.18

Lauda

legendary

Activity: 2674

Merit: 2965

Terminated.

Here are two new banlists that bans spy nodes as well as S2X attack clusters on AWS & co.:
GUI:

Code:

setban 101.201.53.37 add 31557600
setban 103.3.61.48 add 31557600
setban 104.154.111.175 add 31557600
setban 104.222.22.161 add 31557600
setban 114.55.29.227 add 31557600
setban 119.9.116.68 add 31557600
setban 120.24.37.119 add 31557600
setban 120.55.171.74 add 31557600
setban 128.8.124.7 add 31557600
setban 129.13.252.36 add 31557600
setban 129.13.252.47 add 31557600
setban 131.114.88.218 add 31557600
setban 13.59.128.171 add 31557600
setban 13.59.180.243 add 31557600
setban 136.243.139.120 add 31557600
setban 138.197.194.32 add 31557600
setban 138.197.195.32 add 31557600
setban 138.197.195.52 add 31557600
setban 138.197.197.108 add 31557600
setban 138.197.197.132 add 31557600
setban 138.197.197.152 add 31557600
setban 138.197.197.164 add 31557600
setban 138.197.197.174 add 31557600
setban 138.197.197.179 add 31557600
setban 138.197.197.50 add 31557600
setban 138.197.198.120 add 31557600
setban 138.197.201.197 add 31557600
setban 138.197.203.66 add 31557600
setban 138.197.203.86 add 31557600
setban 138.197.211.234 add 31557600
setban 138.201.18.26 add 31557600
setban 138.68.10.138 add 31557600
setban 139.162.96.165 add 31557600
setban 148.251.151.71 add 31557600
setban 159.203.59.209 add 31557600
setban 171.100.25.191 add 31557600
setban 173.232.228.146 add 31557600
setban 174.129.116.81 add 31557600
setban 180.173.203.229 add 31557600
setban 185.185.41.6 add 31557600
setban 188.116.17.178 add 31557600
setban 188.116.56.84 add 31557600
setban 188.195.105.36 add 31557600
setban 188.65.213.21 add 31557600
setban 190.147.110.61 add 31557600
setban 190.88.224.236 add 31557600
setban 190.88.227.234 add 31557600
setban 190.88.231.42 add 31557600
setban 192.99.69.179 add 31557600
setban 194.230.155.245 add 31557600
setban 198.211.117.235 add 31557600
setban 202.108.211.56 add 31557600
setban 204.236.202.17 add 31557600
setban 205.251.22.236 add 31557600
setban 205.251.85.156 add 31557600
setban 205.251.85.157 add 31557600
setban 223.220.112.31 add 31557600
setban 24.108.150.215 add 31557600
setban 24.184.39.126 add 31557600
setban 24.48.79.56 add 31557600
setban 31.146.211.3 add 31557600
setban 34.209.138.25 add 31557600
setban 34.212.140.4 add 31557600
setban 34.231.206.193 add 31557600
setban 35.187.10.3 add 31557600
setban 35.189.224.29 add 31557600
setban 35.189.241.70 add 31557600
setban 35.196.46.145 add 31557600
setban 45.32.117.240 add 31557600
setban 45.33.65.130 add 31557600
setban 45.33.95.186 add 31557600
setban 46.101.160.168 add 31557600
setban 46.166.175.44 add 31557600
setban 46.63.26.63 add 31557600
setban 47.52.41.23 add 31557600
setban 47.88.49.242 add 31557600
setban 47.88.57.29 add 31557600
setban 47.89.179.74 add 31557600
setban 47.90.4.203 add 31557600
setban 47.90.97.52 add 31557600
setban 47.91.74.77 add 31557600
setban 47.91.77.119 add 31557600
setban 47.91.89.32 add 31557600
setban 47.93.173.17 add 31557600
setban 47.95.213.15 add 31557600
setban 52.14.135.10 add 31557600
setban 52.72.52.99 add 31557600
setban 54.166.177.141 add 31557600
setban 54.200.90.164 add 31557600
setban 54.201.12.166 add 31557600
setban 54.218.119.167 add 31557600
setban 54.223.136.62 add 31557600
setban 54.245.51.127 add 31557600
setban 54.252.134.21 add 31557600
setban 54.252.238.189 add 31557600
setban 59.110.63.71 add 31557600
setban 64.137.146.240 add 31557600
setban 66.177.77.213 add 31557600
setban 71.171.127.198 add 31557600
setban 72.36.89.11 add 31557600
setban 73.218.245.30 add 31557600
setban 74.124.33.10 add 31557600
setban 79.138.134.192 add 31557600
setban 80.92.178.116 add 31557600
setban 82.130.103.18 add 31557600
setban 85.180.177.90 add 31557600
setban 86.120.188.134 add 31557600
setban 94.16.71.71 add 31557600
setban 94.16.73.112 add 31557600
setban 99.237.228.185 add 31557600

CLI:

Code:

./bitcoin-cli setban 101.201.53.37 add 31557600
./bitcoin-cli setban 103.3.61.48 add 31557600
./bitcoin-cli setban 104.154.111.175 add 31557600
./bitcoin-cli setban 104.222.22.161 add 31557600
./bitcoin-cli setban 114.55.29.227 add 31557600
./bitcoin-cli setban 119.9.116.68 add 31557600
./bitcoin-cli setban 120.24.37.119 add 31557600
./bitcoin-cli setban 120.55.171.74 add 31557600
./bitcoin-cli setban 128.8.124.7 add 31557600
./bitcoin-cli setban 129.13.252.36 add 31557600
./bitcoin-cli setban 129.13.252.47 add 31557600
./bitcoin-cli setban 131.114.88.218 add 31557600
./bitcoin-cli setban 13.59.128.171 add 31557600
./bitcoin-cli setban 13.59.180.243 add 31557600
./bitcoin-cli setban 136.243.139.120 add 31557600
./bitcoin-cli setban 138.197.194.32 add 31557600
./bitcoin-cli setban 138.197.195.32 add 31557600
./bitcoin-cli setban 138.197.195.52 add 31557600
./bitcoin-cli setban 138.197.197.108 add 31557600
./bitcoin-cli setban 138.197.197.132 add 31557600
./bitcoin-cli setban 138.197.197.152 add 31557600
./bitcoin-cli setban 138.197.197.164 add 31557600
./bitcoin-cli setban 138.197.197.174 add 31557600
./bitcoin-cli setban 138.197.197.179 add 31557600
./bitcoin-cli setban 138.197.197.50 add 31557600
./bitcoin-cli setban 138.197.198.120 add 31557600
./bitcoin-cli setban 138.197.201.197 add 31557600
./bitcoin-cli setban 138.197.203.66 add 31557600
./bitcoin-cli setban 138.197.203.86 add 31557600
./bitcoin-cli setban 138.197.211.234 add 31557600
./bitcoin-cli setban 138.201.18.26 add 31557600
./bitcoin-cli setban 138.68.10.138 add 31557600
./bitcoin-cli setban 139.162.96.165 add 31557600
./bitcoin-cli setban 148.251.151.71 add 31557600
./bitcoin-cli setban 159.203.59.209 add 31557600
./bitcoin-cli setban 171.100.25.191 add 31557600
./bitcoin-cli setban 173.232.228.146 add 31557600
./bitcoin-cli setban 174.129.116.81 add 31557600
./bitcoin-cli setban 180.173.203.229 add 31557600
./bitcoin-cli setban 185.185.41.6 add 31557600
./bitcoin-cli setban 188.116.17.178 add 31557600
./bitcoin-cli setban 188.116.56.84 add 31557600
./bitcoin-cli setban 188.195.105.36 add 31557600
./bitcoin-cli setban 188.65.213.21 add 31557600
./bitcoin-cli setban 190.147.110.61 add 31557600
./bitcoin-cli setban 190.88.224.236 add 31557600
./bitcoin-cli setban 190.88.227.234 add 31557600
./bitcoin-cli setban 190.88.231.42 add 31557600
./bitcoin-cli setban 192.99.69.179 add 31557600
./bitcoin-cli setban 194.230.155.245 add 31557600
./bitcoin-cli setban 198.211.117.235 add 31557600
./bitcoin-cli setban 202.108.211.56 add 31557600
./bitcoin-cli setban 204.236.202.17 add 31557600
./bitcoin-cli setban 205.251.22.236 add 31557600
./bitcoin-cli setban 205.251.85.156 add 31557600
./bitcoin-cli setban 205.251.85.157 add 31557600
./bitcoin-cli setban 223.220.112.31 add 31557600
./bitcoin-cli setban 24.108.150.215 add 31557600
./bitcoin-cli setban 24.184.39.126 add 31557600
./bitcoin-cli setban 24.48.79.56 add 31557600
./bitcoin-cli setban 31.146.211.3 add 31557600
./bitcoin-cli setban 34.209.138.25 add 31557600
./bitcoin-cli setban 34.212.140.4 add 31557600
./bitcoin-cli setban 34.231.206.193 add 31557600
./bitcoin-cli setban 35.187.10.3 add 31557600
./bitcoin-cli setban 35.189.224.29 add 31557600
./bitcoin-cli setban 35.189.241.70 add 31557600
./bitcoin-cli setban 35.196.46.145 add 31557600
./bitcoin-cli setban 45.32.117.240 add 31557600
./bitcoin-cli setban 45.33.65.130 add 31557600
./bitcoin-cli setban 45.33.95.186 add 31557600
./bitcoin-cli setban 46.101.160.168 add 31557600
./bitcoin-cli setban 46.166.175.44 add 31557600
./bitcoin-cli setban 46.63.26.63 add 31557600
./bitcoin-cli setban 47.52.41.23 add 31557600
./bitcoin-cli setban 47.88.49.242 add 31557600
./bitcoin-cli setban 47.88.57.29 add 31557600
./bitcoin-cli setban 47.89.179.74 add 31557600
./bitcoin-cli setban 47.90.4.203 add 31557600
./bitcoin-cli setban 47.90.97.52 add 31557600
./bitcoin-cli setban 47.91.74.77 add 31557600
./bitcoin-cli setban 47.91.77.119 add 31557600
./bitcoin-cli setban 47.91.89.32 add 31557600
./bitcoin-cli setban 47.93.173.17 add 31557600
./bitcoin-cli setban 47.95.213.15 add 31557600
./bitcoin-cli setban 52.14.135.10 add 31557600
./bitcoin-cli setban 52.72.52.99 add 31557600
./bitcoin-cli setban 54.166.177.141 add 31557600
./bitcoin-cli setban 54.200.90.164 add 31557600
./bitcoin-cli setban 54.201.12.166 add 31557600
./bitcoin-cli setban 54.218.119.167 add 31557600
./bitcoin-cli setban 54.223.136.62 add 31557600
./bitcoin-cli setban 54.245.51.127 add 31557600
./bitcoin-cli setban 54.252.134.21 add 31557600
./bitcoin-cli setban 54.252.238.189 add 31557600
./bitcoin-cli setban 59.110.63.71 add 31557600
./bitcoin-cli setban 64.137.146.240 add 31557600
./bitcoin-cli setban 66.177.77.213 add 31557600
./bitcoin-cli setban 71.171.127.198 add 31557600
./bitcoin-cli setban 72.36.89.11 add 31557600
./bitcoin-cli setban 73.218.245.30 add 31557600
./bitcoin-cli setban 74.124.33.10 add 31557600
./bitcoin-cli setban 79.138.134.192 add 31557600
./bitcoin-cli setban 80.92.178.116 add 31557600
./bitcoin-cli setban 82.130.103.18 add 31557600
./bitcoin-cli setban 85.180.177.90 add 31557600
./bitcoin-cli setban 86.120.188.134 add 31557600
./bitcoin-cli setban 94.16.71.71 add 31557600
./bitcoin-cli setban 94.16.73.112 add 31557600
./bitcoin-cli setban 99.237.228.185 add 31557600

Posted by G. Maxwell:
https://people.xiph.org/~greg/banlist.gui.txt
https://people.xiph.org/~greg/banlist.cli.txt

Meuh6879

legendary

Activity: 1512

Merit: 1012

From 2017-09-01 to 2017-09-19

Code:

100.35.27.249
104.128.94.12
104.155.122.212
106.117.151.89
106.186.31.140
106.75.146.143
109.225.25.187

115.132.248.36
118.93.103.208
121.86.50.33
128.70.191.84
128.8.124.7
129.13.252.36
129.13.252.47

136.243.139.120
136.243.139.96
142.105.252.237
145.132.191.135
146.120.56.238
146.60.38.249
159.224.90.59
162.250.221.238
170.79.45.59
173.212.193.11
173.245.203.184
173.255.251.118
176.104.14.35
178.255.153.166

181.59.126.46
184.207.138.127
184.98.248.101
185.59.58.157
187.65.144.146
187.75.50.120
188.163.74.12
188.192.250.36
188.234.228.62
188.37.67.242
188.65.213.21

195.91.160.170
198.48.223.50
200.0.51.232
200.114.199.78
2001:0:5ef5:79fb:147c:1e50:6b00:9ebf
202.108.211.56
203.220.88.53
203.3.109.194
205.251.22.236

212.108.43.57
212.159.113.138
213.220.247.85
213.55.211.9
216.19.183.58
217.61.217.125
218.226.212.4
218.87.96.161
222.93.10.16

24.119.224.62
24.18.147.55

2607:5300:60:1bd1::1
2a00:1398:4:2a00::a1
2a00:1398:4:2a00::a5
2a03:b0c0:3:d0::5c9:4001

31.223.227.198
31.36.66.102
35.187.187.248
35.189.230.22
37.135.34.116
37.15.117.117
37.201.240.133
37.229.201.178

45.33.65.130
46.101.246.115
47.223.222.114
47.89.252.244
47.90.4.203
47.93.23.68
49.84.247.96

5.165.16.34
50.66.58.222

60.175.104.134
62.47.222.32
62.87.203.34
69.84.31.75

70.30.104.212
71.84.104.6
72.36.89.11
73.222.196.104
74.132.27.118
74.207.240.152
76.254.56.180
78.106.11.204
78.146.56.214
78.46.79.17
78.99.22.173
79.169.200.81
79.73.36.52

80.100.203.151
81.111.144.79
81.171.56.134
83.161.249.125
83.169.228.178
83.243.39.142
84.23.44.69
84.242.74.251
84.29.73.246
87.120.1.28
87.214.171.55

91.106.149.46
91.78.240.152
93.202.6.16
93.219.134.103
93.75.30.249
94.100.213.84
94.103.228.161
95.29.41.93
98.221.120.90

jackg

copper member

Activity: 2856

Merit: 3071

https://bit.ly/387FXHi lightning theory

Quote from: zx9r on August 01, 2017, 07:55:10 PM

My bitcoin node is receiving connections from

2a00:1398:4:2a00::a1
2a00:1398:4:2a00::a5
2001:0:4137:9e76:2877:25aa:51c2

on port 8333

I dont understand how I am receiving this connections because I have port 8333 closed in my ADSL router.
I have tested from https://bitnodes.21.co/ to check my node and it says it is not available, which is correct as I say the port is closed in the router.

So, how can my node be reachable by those addresses at port 8333 ? May be because IPv6 and an error in my router ?

PS: in case it helps: user-agent for that connections is Satoshi:0.9.99

Maybe these connections are going through a different port into your node.

If you want me to, if you send me your IP (via PM) I'll test your 8333 port to check nothing is live through it. If you don't want to share your IP then that's fine also.

Meuh6879

legendary

Activity: 1512

Merit: 1012

From 2017-07-08 to 2017-08-10.

Code:

100.35.27.249
106.117.151.89
106.186.31.140
106.75.146.143
115.132.248.36

121.86.50.33
128.8.124.7
129.13.252.36
129.13.252.47

136.243.139.120
136.243.139.96
142.105.252.237
145.132.191.135
146.120.56.238

162.250.221.238
170.79.45.59
173.212.193.11
173.245.203.184
173.255.251.118
176.104.14.35
178.255.153.166

184.207.138.127
184.98.248.101
185.59.58.157
187.65.144.146
188.163.74.12
188.37.67.242
188.65.213.21

195.91.160.170
198.48.223.50

2001:0:5ef5:79fb:147c:1e50:6b00:9ebf
202.108.211.56
203.220.88.53
205.251.22.236
212.159.113.138
213.220.247.85
213.55.211.9
217.61.217.125
218.226.212.4
218.87.96.161
222.93.10.16

24.119.224.62
24.18.147.55

2607:5300:60:1bd1::1
2a00:1398:4:2a00::a1
2a00:1398:4:2a00::a5
2a03:b0c0:3:d0::5c9:4001

31.223.227.198
35.187.187.248
35.189.230.22
37.135.34.116
37.15.117.117
37.201.240.133

45.33.65.130
46.101.246.115
47.90.4.203
47.93.23.68
49.84.247.96
50.66.58.222

62.47.222.32
62.87.203.34
70.30.104.212
72.36.89.11
73.222.196.104
74.132.27.118
78.146.56.214
78.146.56.214
78.46.79.17
79.169.200.81

80.100.203.151
81.111.144.79
81.171.56.134
83.161.249.125
83.169.228.178
83.243.39.142
84.23.44.69
84.242.74.251
87.120.1.28
87.214.171.55

93.75.30.249
95.29.41.93
98.221.120.90

zx9r

full member

Activity: 153

Merit: 100

I have just read it can be something related to Teredo tunneling: https://en.wikipedia.org/wiki/Teredo_tunneling

Can this compromise my node ?

zx9r

full member

Activity: 153

Merit: 100

My bitcoin node is receiving connections from

2a00:1398:4:2a00::a1
2a00:1398:4:2a00::a5
2001:0:4137:9e76:2877:25aa:51c2

on port 8333

I dont understand how I am receiving this connections because I have port 8333 closed in my ADSL router.
I have tested from https://bitnodes.21.co/ to check my node and it says it is not available, which is correct as I say the port is closed in the router.

So, how can my node be reachable by those addresses at port 8333 ? May be because IPv6 and an error in my router ?

PS: in case it helps: user-agent for that connections is Satoshi:0.9.99

Meuh6879

legendary

Activity: 1512

Merit: 1012

From 2017-06-18 to 2017-07-07.
New method to survey (less noise, less arbitrary ban).

Code:

129.13.252.36
129.13.252.47

136.243.139.120
145.132.191.135
162.250.221.238

173.255.251.118
176.104.14.35
178.255.153.166

188.163.74.12
188.65.213.21

2001:0:5ef5:79fb:147c:1e50:6b00:9ebf

202.108.211.56
213.220.247.85
24.18.147.55

2607:5300:60:1bd1::1
2a00:1398:4:2a00::a1
2a00:1398:4:2a00::a5
2a03:b0c0:3:d0::5c9:4001

37.15.117.117

45.33.65.130
47.90.4.203
47.93.23.68

50.66.58.222

73.222.196.104
74.132.27.118
79.169.200.81

83.169.228.178
84.242.74.251

93.75.30.249
98.221.120.90

Harry Callahan

sr. member

Activity: 350

Merit: 250

Quote from: Hydrogen on May 08, 2017, 04:47:49 PM

Quote from: btcney on May 08, 2017, 04:36:41 PM

Do you think that BU is actually trying to attack the bitcoin network? I'm a little confused as to what the attack in this threads purpose even is.
I still have learning to do regarding deeper levels of bitcoin opposed to just knowing how to buy and sell... I hope this attack gets wiped, and whoever founded it, be it BU or anyone else gets found out and we somehow find a solution to keep them from being able to do it again. If it is bitcoin unlimited does that mean they really are trying to turn bitcoin towards there individual goals and ruin bitcoin for everyone else? I dislike the idea of any exclusive group getting to be at the top of bitcoin.

BU claims they can fix these attacks with larger blocks. They could gain from these attacks. Another possibility is the network attack is used to manipulate the market, push btc price down so people can buy lower & profit.
If only core and segwit nodes were being attacked, that could be evidence BU was behind this.

You really cannot come to a conclusion just like that,i am not sure about the reasons for these sort of attacks but one thing is sure that it could drive the price of bitcoin really low and the network is really not capable to withstand these attacks in the fist place as it will clog the entire network,greed is driving people to do these kind of silly activities,so it might be the involvement of any government to create uncertainty in bitcoin.

Hydrogen

legendary

Activity: 2562

Merit: 1441

Quote from: btcney on May 08, 2017, 04:36:41 PM

Do you think that BU is actually trying to attack the bitcoin network? I'm a little confused as to what the attack in this threads purpose even is.
I still have learning to do regarding deeper levels of bitcoin opposed to just knowing how to buy and sell... I hope this attack gets wiped, and whoever founded it, be it BU or anyone else gets found out and we somehow find a solution to keep them from being able to do it again. If it is bitcoin unlimited does that mean they really are trying to turn bitcoin towards there individual goals and ruin bitcoin for everyone else? I dislike the idea of any exclusive group getting to be at the top of bitcoin.

BU claims they can fix these attacks with larger blocks. They could gain from these attacks. Another possibility is the network attack is used to manipulate the market, push btc price down so people can buy lower & profit.

If only core and segwit nodes were being attacked, that could be evidence BU was behind this.

btcney

hero member

Activity: 588

Merit: 500

Quote from: Hydrogen on May 08, 2017, 03:26:45 PM

Is there a way to know if only non BU nodes are being attacked?

It would seem BU has the most to gain from this given they haven't managed to fix their node drop bug .

Do you think that BU is actually trying to attack the bitcoin network? I'm a little confused as to what the attack in this threads purpose even is.
I still have learning to do regarding deeper levels of bitcoin opposed to just knowing how to buy and sell... I hope this attack gets wiped, and whoever founded it, be it BU or anyone else gets found out and we somehow find a solution to keep them from being able to do it again. If it is bitcoin unlimited does that mean they really are trying to turn bitcoin towards there individual goals and ruin bitcoin for everyone else? I dislike the idea of any exclusive group getting to be at the top of bitcoin.

Hydrogen

legendary

Activity: 2562

Merit: 1441

Is there a way to know if only non BU nodes are being attacked?

It would seem BU has the most to gain from this given they haven't managed to fix their node drop bug .

Meuh6879

legendary

Activity: 1512

Merit: 1012

are you read debug.log and ban randomly client (to find) ?
no ? so, you don't see the whole network ...

not a problem for me.
just a normal study of the situation.

The One

legendary

Activity: 924

Merit: 1000

You guys must be unpopular to get attacks... i don't get any Roll Eyes

Meuh6879

legendary

Activity: 1512

Merit: 1012

From 2017-04-27 to 2017-05-08 (12 days)

Code:

129.13.252.47 Hits = 11562
129.13.252.36 Hits = 9182
188.65.213.21 Hits = 5614
46.101.246.115 Hits = 4212
136.243.139.96 Hits = 3948
139.162.96.165 Hits = 3295
[2a03:b0c0:3:d0::5c9:4001] Hits = 2665
[2a00:1398:4:2a00::a5] Hits = 1303
[2a00:1398:4:2a00::a1] Hits = 1045
104.196.107.156 Hits = 730
54.223.77.14 Hits = 696
52.29.215.16 Hits = 690
52.70.130.28 Hits = 636
52.76.95.246 Hits = 581
52.74.14.245 Hits = 531
104.236.95.174 Hits = 522
192.99.19.37 Hits = 518
54.94.211.146 Hits = 494
52.192.180.114 Hits = 479
52.210.89.26 Hits = 470
[2604:a880:800:10::7ee:5001] Hits = 459
52.18.56.236 Hits = 421
52.8.99.184 Hits = 391
52.62.33.159 Hits = 341
72.36.89.11 Hits = 272
[2001:0:9d38:90d7:ac:3a9c:fab0:b4fa] Hits = 269
[2001:19f0:ac01:2fb:5400:ff:fe5b:c3ff] Hits = 246
52.32.80.148 Hits = 218
46.63.26.63 Hits = 162
131.114.88.218 Hits = 137
202.170.57.251 Hits = 111
5.189.177.237 Hits = 99
90.126.106.129 Hits = 53
109.252.107.129 Hits = 45
84.9.11.75 Hits = 40
124.65.117.206 Hits = 34
14.3.29.141 Hits = 33
190.88.224.137 Hits = 27
86.175.16.118 Hits = 22
49.159.52.156 Hits = 20
45.16.139.115 Hits = 18

Same list, IP Range ordered :

Code:

[2001:0:9d38:90d7:ac:3a9c:fab0:b4fa] Hits = 269
[2001:19f0:ac01:2fb:5400:ff:fe5b:c3ff] Hits = 246
[2604:a880:800:10::7ee:5001] Hits = 459
[2a00:1398:4:2a00::a1] Hits = 1045
[2a00:1398:4:2a00::a5] Hits = 1303
[2a03:b0c0:3:d0::5c9:4001] Hits = 2665
104.196.107.156 Hits = 730
104.236.95.174 Hits = 522
109.252.107.129 Hits = 45
124.65.117.206 Hits = 34
129.13.252.36 Hits = 9182
129.13.252.47 Hits = 11562
131.114.88.218 Hits = 137
136.243.139.96 Hits = 3948
139.162.96.165 Hits = 3295
14.3.29.141 Hits = 33
188.65.213.21 Hits = 5614
190.88.224.137 Hits = 27
192.99.19.37 Hits = 518
202.170.57.251 Hits = 111
45.16.139.115 Hits = 18
46.101.246.115 Hits = 4212
46.63.26.63 Hits = 162
49.159.52.156 Hits = 20
5.189.177.237 Hits = 99
52.18.56.236 Hits = 421
52.192.180.114 Hits = 479
52.210.89.26 Hits = 470
52.29.215.16 Hits = 690
52.32.80.148 Hits = 218
52.62.33.159 Hits = 341
52.70.130.28 Hits = 636
52.74.14.245 Hits = 531
52.76.95.246 Hits = 581
52.8.99.184 Hits = 391
54.223.77.14 Hits = 696
54.94.211.146 Hits = 494
72.36.89.11 Hits = 272
84.9.11.75 Hits = 40
86.175.16.118 Hits = 22
90.126.106.129 Hits = 53

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: bitbunnny on April 22, 2017, 10:09:44 AM

Quote from: countryfree on April 04, 2017, 04:35:23 PM

We've all seen that BTC is getting more and more centralized, and I wonder if the people behind this attack could be trying to push even further into that direction. There are still some lonely individuals running a node at their home, and the attacker may want to make this next to impossible, as running a node should now command close and regular monitoring. So only large teams, or mining farms (from some large eastern country), with staff on guard would be able to run nodes efficiently. See what I mean?

Does that make sense?

It could make sense if it's true that there sre some interest groups or individuals who would like to see Bitcoin fully centralized because that would mean the control and power. In their hands, of course. But what confuses me is the question if this is realy possible, could happen that bi becomes centralized?

Yes, Bitcoin could become centalized if its no longer feasible or affordable for "normal" people to run full nodes. This attack however is not strong enough to do so and even if it was in its strongest possible form (fully saturating all connection slots of a given target) it would have a different effect. This is a very weak sybil/(D)DoS attack. Once detected there is no need for "staff on guard" as countryfree puts it, you just ban the IP addresses of the attacker and your node goes back to normal business.

bitbunnny

legendary

Activity: 2912

Merit: 1068

WOLF.BET - Provably Fair Crypto Casino

Quote from: countryfree on April 04, 2017, 04:35:23 PM

We've all seen that BTC is getting more and more centralized, and I wonder if the people behind this attack could be trying to push even further into that direction. There are still some lonely individuals running a node at their home, and the attacker may want to make this next to impossible, as running a node should now command close and regular monitoring. So only large teams, or mining farms (from some large eastern country), with staff on guard would be able to run nodes efficiently. See what I mean?

Does that make sense?

It could make sense if it's true that there sre some interest groups or individuals who would like to see Bitcoin fully centralized because that would mean the control and power. In their hands, of course. But what confuses me is the question if this is realy possible, could happen that bi becomes centralized?

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: countryfree on April 04, 2017, 04:35:23 PM

We've all seen that BTC is getting more and more centralized, and I wonder if the people behind this attack could be trying to push even further into that direction. There are still some lonely individuals running a node at their home, and the attacker may want to make this next to impossible, as running a node should now command close and regular monitoring. So only large teams, or mining farms (from some large eastern country), with staff on guard would be able to run nodes efficiently. See what I mean?

Does that make sense?

No, this attack is not strong enough to impact a node. It will not saturate connection slots and I suspect home run nodes to change IP-Addresses more frequently thus further limiting the impact of the attack. I had these connections on my home run node, but I wouldnt have noticed them there.

countryfree

legendary

Activity: 3066

Merit: 1047

Your country may be your worst enemy

We've all seen that BTC is getting more and more centralized, and I wonder if the people behind this attack could be trying to push even further into that direction. There are still some lonely individuals running a node at their home, and the attacker may want to make this next to impossible, as running a node should now command close and regular monitoring. So only large teams, or mining farms (from some large eastern country), with staff on guard would be able to run nodes efficiently. See what I mean?

Does that make sense?

andrew24p

sr. member

Activity: 378

Merit: 250

Someone has been attacking the mempool for years to push their bigger block agenda, which is why we see so many small transactions in cycles.

Topic: [Spy Nodes && S2X] Attack on the Network in Progress (Read 7571 times)