DDoS Attacks .:. WorkerBee PH-Pool Week 241
I remember the days when DDoS attacks were something worse than could happen to a server/network administrator... There was no good protection against them, or if there was, it was super-expensive and affordable only for big companies with huge budgets... But, on the other side, to "execute" the DDoS attack, you needed a bot network with tons of different IPs, from various locations, and all that cost a lot of money! So, even if you wanted to harm someone, you needed a lot of money to do it...
I also remember that back in the days, I had some crazy good machines for my clients, and sometimes, these DDoS attacks weren't good enough to overwhelm the machine and to cause bigger harm... So, there was a possibility to "beat" the attacker... To have better cards in the hand...

Created on Canva.com, using my photo as a background
A distributed denial-of-service (DDoS) attack is a malicious attempt to disrupt the normal traffic of a targeted server, service, or network by overwhelming the target or its surrounding infrastructure with a flood of Internet traffic.
source: https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/
As the Internet was growing, more networks were added, more IPs, more machines, more bots, etc. These attacks became stronger and stronger... A few decades ago, these attacks were short, 15-30 minutes... as they were expensive... Today, they can last for hours and hours, if not even days! Truth to be told, the prevention tools also became more powerful, successfully mitigating attacks, but not always...

In the last few weeks, I did have a couple of these on my hosting machine that I described in my recent post... Some of them were mitigated by my hosting company, others weren't... Cloudflare can be useful too... So, if you don't have any protection, maybe it's not a bad idea to try CF service... They have a free option too, and it can help a bit...
Unfortunately, after having issues on my hosting side, from yesterday, someone is targeting "public" Hive-Engine nodes with DDoS attacks! If you had problems in the last 24-48 hours with Hive-Engine, history nodes, that is the reason behind it... Is there a solution for these attacks? Tweaking scripts, having more powerful machines, and limiting resources can help... But, both sides are working at the same time... Hackers and app developers...
Who will win? Why do these DDoS attacks even exist? I don't know... Sometimes, hackers do it to try to find the "way in" to the infrastructure, to make some benefits in the long run... Also, many shady things can happen... People are jealous of each other, envy, or there can be a competition doing it... Rival blockchain? Who knows... The only thing that we can do is to try to prevent them in the future, and to minimize the damage as much as possible... Bad people and bad actors in the space will always exist...

Let's see the WorkerBee Pool numbers for this week...
This week, we have mined 82 BEE tokens in total, 11 less than the week before! 🙁
This week, we didn't get new delegators! On the other side, we got new delegations from old members, as usual! Thanks, guys! Appreciate your support!
This POOL doesn't have fees, and you get up to 20% MORE by delegating to it!



What about the bonus tokens?
This week, it's time for distributing some LEN tokens as our BONUS reward! You probably know the background of the token as I'm one of the co-owners of the Liotes project, where LEN is one of the two official tokens... As LEN tokens have a small inflation that comes from LENM miners, the token price is pretty stable, indexed in HIVE... There are 2 diesel pools where users can provide liquidity, and in one of them, they can earn additional rewards (besides FEEs collected from transactions)! Some of the rewards are very interesting, so more and more people decide to put those LEN (and LENM) tokens to work, creating passive income...
There will be distributed 55 LEN tokens to the delegators of the pool as a bonus reward today!

55 LEN tokens will be distributed as a bonus... The APR (without the bonus) was 10.107%, and when we added the bonus, it went up to 12.119%!
I have calculated the ROI approximately with medium prices for all tokens when creating this post... So, those numbers are valid if you bought WB and sold BEE tokens at the middle HiveEngine price...
Do you want to sponsor the PH-Pool with your tokens, receive a short SPONSORED segment in this post, and raise awareness about your front-end or dApp? Please let me know in the comment section, or contact me through Discord or Twitter, and we will find the best solution for both parties...

If you want to join the WorkerBee PH-Pool, the only thing that you have to do is to STAKE tokens to YOUR account and DELEGATE your staked WORKERBEE tokens to THIS account (@ph1102)! Every week, you will get your portion of mined BEE tokens and BONUS rewards!
.:. DO NOT STAKE TOKENS TO MY ACCOUNT!!! Just DELEGATE! .:.

All payments will be made after publishing this post...
If you have any questions, please leave them in the comment section!
You can find more about this pool in the initial post here https://ecency.com/hive-119826/@ph1102/workerbee-p-h-ool-let-s-help-each-other.
Thank you for your time.
--ph--
None of this is financial advice!!!

👉 Vote for Liotes HIVE Witness HERE 👈
Don't forget to follow, reblog, and browse my Hivepage to stay connected with all the great stuff!
DDOS is going to be a bigger problem since people use more and more IOT without changing the standard PW or updating firmware .
back to your post this got me wondering ... : There are 2 diesel pools where users can provide liquidity, and in one of them, they can earn additional rewards (besides FEEs collected from transactions)!
are we now running a petrol station ????
Now imagine all that combined with some AI tech, learned to hack... 😨
Hehehehe... I hope not... As with these laws regarding electric cars, petrol stations will go out of business... 😀
one of the reasons i use PFsense as my router on proxmox :)
I wouldn't really want to run my own web site these days as it is likely to get attacked. There are so many crooks out there and they control lots of other machines that they may have hacked. I hope the Hive team can find ways to resist the attacks. It has happened before.
This time, it's Hive-Engine under attack, but you never know what comes next... Doing things out there makes us targets... Unfortunately, bad people exist, but the majority is still good... We will win! 😃
Thank you for the LEN!
You are welcome! Thanks for your delegation!
I think they target hive engine just to being annoying, maybe someone like from blurt or steem
That could be a case... People are strange... 😃
It's annoying to see people do DDOS attacks. I don't think it helps anyone, and I did notice that Hive-Engine was slow over the weekend.
Thanks for running the pool and for the BEE/LEN tokens.
Hopefully, the attackers will get bored and stop wasting their (and our) time...
I didn't know to the full extent what's happening with Hive Engine, noticed something similar did happen some time back. Have a withdrawal stuck there for a day now, will learn better to use different bridges next time around. Hopefully it gets resolved soon and the system becomes more resilient.
Back then was a bit different as a certain account was flooding the chain with micro transactions... That was fixed by changing the code... DDoS attacks are a bit different, as they hit the network directly, and they are hard to "isolate"... Anyway, we will see how it goes in the next days... For now, attacks are happening multiple times per day, but they are relatively short...
The real problem happens when they last for a couple of hours, or days... Hopefully not in our case
Hopefully indeed! Perhaps then, like you mentioned on the post, using Cloudfare services could limit the number of hits on the network? Maybe through the frontends or that wouldn't be much effective?
The withdrawal has been processed recently, thank goodness.
Frontends are a bit different than running a node...
Currently, I'm testing CloudFlare options... will see if it helps...
I was trying to look up some history on transactions yesterday and noticed transactions for the last couple of days were not available. It appears to be up to date now. I don't know why bad actors would target Hive engine.
Yeah, that was a separate issue... The official history node of Hive-Engine was down... It should be OK now...
Thanks for letting us know what's been going on with the HE nodes. There is one good thing about the whole thing. DDoS attacks usually happen when a target becomes interesting to the attackers for some reason.
I don't know anymore... I emptied my hosting server a week ago and now it hosts only 2 small websites with almost 0 traffic... and it got hit today by 8 8-hour DDoS attack... It makes no sense... There is no reason at all...
The big problem is that these DDoS attacks have become very cheap and anyone can "order" (or run) one... I hope there will be effective tools developed soon, as this is getting out of control...
In your case, it probably became a personal matter for the hacker because he wasn't able to fully take control of the server or whatever might be in their twisted minds. You are right that DDoS is much cheaper to perform these days, but bad guys also became more sophisticated. DDoS is brute force and basically tells the target it's being attacked. Other methods are more insidious.
Yes, these DDoS attacks are still really annoying. Ecency experiences them occasionally...thanks for BEE.
They are annoying... And they are occurring more and more everywhere... I hope there will be better tools developed to combat them...