This time our billing system is being attacked via a DDOS intended for resource exhaustion.

Hence our billing system is working a little bit slower than usual right now, we are working on it.

First the spam attacks, now this. This type of thing always tends to happen when are running specials.

Current list of shame -- will update later, these are the first ones we have looked on and verified to have inordinate amounts of requests.


Once subnets based on this list were blocked it ended. The whois details are rather interesting and point to a competiting seedbox provider. This seedbox provider also has IPv4 renting business. Some are straight under them, some are on their personal names, and some are just a generic probably holding for the IPv4 addresses. Very few have rDNS setup, those which have looks like spammy or are related to a larger hosting business interestingly enough. Almost all of them are housed at Leaseweb, where this competitors production servers reside almost solely at. Quite frankly, everything seems to be pointing towards them.


Those behind this stopped promptly communicating with us once we pointed out they were behind this. The competiting provider is Rapid Seedbox. We were willing to give them the benefit of the doubt, but they stopped responding to any communication. Their initial response was unexpectedly swift and quick, but once it was obvious everything points to them -- zero responses.
You can verify this yourself by whois'ng some of the IPs, here are examples pointing directly to Rapid Seedbox:,, and

One of the owners of Rapid Seedbox is "[PRIVACY PROTECTION]", many of these subnets are owned by "[PRIVACY PROTECTION]". Googling this name yields many interesting abuse db results, with multiple claims of "hacking gmail", ie. probably bruteforcing passwords like on this attack.
Other owner is named only one of the subnets as i can see. [PRIVACY PROTECTION] is named on multiple ones.
Almost none have rDNS set as of few hours ago. Almost all IPs are hosted at Leaseweb, where Rapid Seedbox has their servers.

Giving them the benefit of the doubt we did not immediately release this, it could've been their whole network is compromised. However, if they stopped communicating and their supposedly 15 people full time staff neither responds, while they pride themselves on super fast help support response time -- It smells fishy.

Normal attack like this, done by botnet and compromised systems would not be so blatantly obvious. Ssomeone with access to a lot of subnets and can spin up on them a lot of VMs at will has to be done behind this. Normal attacks are typically globally spread etc. and typically all IPs have set reverse dns, most have major ISP IP ownership etc. But all of these are fake sounding names, mostly linked to this "greatworktogether" group, and few of the subnets with very similar style of information are clearly linked to Rapid Seedbox.

To best of our knowledge at this moment, no customer accounts were compromised.

We would like to be wrong, as we've just had lengthy negotiations if we would supply servers to them. First contact they asked if we would sell Pulsed Media to them, but that was a very firm no. We proceeded to converse if vice-versa was possible but did not find common ground. After which we started looking for opportunities to work together, by us supplying to them servers. That neither proceeded anywhere.

There is total of 5977 suspicious IPs but we have to make sure no legitimate user IPs ended up on that list before releasing this whole list.

All of the relevant and important subnets are on the above list. Here are the /24 subnets:

To block these subnets just add them to your firewall as is, or without /24 and subnet

We have not moved to block these IPs on our production servers as there could be actual seedbox end users on these subnets and we would not like to be punishing Rapid Seedbox's customers.

We do not know yet if there is relation to the spam attacks lately as well.

If you have any relevant information, please do contact us.

UPDATE 3: Got a response from Rapid Seedbox very soon after releasing last update. Investigation continues.

UPDATE 4:  Rapid Seedbox says all of these IPs are connected to single customer, and requested personal information for privacy to be removed from earlier update. These names has now been changed to [PRIVACY PROTECTION].

UPDATE 5: Rapid Seedbox response was that 1 customer was behind this, and they have disabled access to on their proxies.  -- A proxy service? That's all the information they gave us.

Further, this attack had some email addresses correct, infact many accounts got failed login attempts from these. How did these attackers have any idea what addresses to try? By random chance it's very difficult to get even 1 hit by randomly trying, nevermind in the hundreds. A lot of them are fairly (think decade old) billing profiles too. That makes us think that the attacker has some seedbox niche email address database to try upon.

In any case, we are still going through the list of these targets, and will reset some people's billing profile passwords to be on the safe side. It's quite a bit of manual work as we do not want to just blanket reset everybody's, but manually look at each of the profiles rather and add them to a list so we may contact them if needed. We want to emphasize that we have no evidence of any compromised account so far. To best our knowledge from looking at the logs, zero accounts were compromised.

Make your own conclusions on this.

Monday, May 4, 2020

« Back