What Happens When Your Open-Source Project Becomes a Target?

What Happens When Your Open-Source Project Becomes a Target?

Recently, I've been working on strengthening MyZubster after detecting unusual traffic directed at the server.

I'm not sharing this because I have all the answers.

I'm sharing it because this is part of building software in the real world.

It Isn't Just About Writing Code

When developers start an open-source project, they usually think about features.

You imagine new ideas, new APIs, better user experiences.

What you don't always imagine is having to think about infrastructure, network traffic, server security, and availability.

As a project grows, these become just as important as the code itself.

What Is a DDoS Attack?

Imagine a small local shop.

Normally, customers enter one by one.

Now imagine thousands of people trying to enter at exactly the same time.

Even if none of them buys anything, the entrance becomes blocked and real customers cannot get inside.

A DDoS (Distributed Denial of Service) attack works in a similar way.

Instead of stealing data, its goal is often to overwhelm a server with so many requests that legitimate users cannot access the service.

Why I'm Being Careful

At the moment, I'm monitoring the situation and collecting information.

I'm also waiting for feedback from Aruba's technical support before deciding the next steps.

Rather than making changes too quickly, I'd prefer to hear their recommendations about the best way to protect the infrastructure while keeping the service available.

Sometimes the best decision isn't the fastest one—it's the one based on good technical advice.

Many hosting providers, including Aruba, offer anti-DDoS protections and recommend evaluating the type of traffic before changing server configurations or enabling additional defensive measures.

What This Experience Taught Me

This situation reminded me that building software doesn't stop when the application works.

You also need to think about:

• monitoring;
• backups;
• logging;
• network protection;
• infrastructure resilience;
• recovery plans.

These are the parts users rarely see, but they are essential for keeping a service online.

Open Source Means Sharing the Journey

One of the reasons I build MyZubster in the open is that people can follow not only the successes, but also the challenges.

Every infrastructure problem becomes a learning opportunity.

Every unexpected event helps improve the project.

Looking Ahead

I'm continuing to improve MyZubster while waiting for Aruba's technical guidance.

Whatever the outcome, this experience will help make the project stronger.

Building open-source software isn't just about creating new features.

It's also about learning how to keep those features available, secure, and reliable for everyone.