Nice big old port scan. Brand new server too. Just a few days old so there is nothing to find. Don’t worry I contacted AWS. Stay safe out there.
You contacted Amazon over a port scan?
Got my first script kiddy
Submitted 3 days ago by MightBeFluffy@pawb.social to selfhosted@lemmy.world
https://pawb.social/pictrs/image/3453d188-d3f2-4e0c-a8c0-9c32c836f1e9.jpeg
Comments
atzanteol@sh.itjust.works 3 days ago
MightBeFluffy@pawb.social 3 days ago
Yes. Don’t port scan my shit.
non_burglar@lemmy.world 3 days ago
Umm…
You know how that works, right? Like, if you don’t want to expose ports, just… don’t expose them. But you can’t prevent port scanning.
I would love to see the support request from AWS for this.
atzanteol@sh.itjust.works 3 days ago
“Good luck with that.”
I realize you’re inexperienced and excited, but this is truly no big deal. Port scans are quite common and aren’t even always malicious. You can use nmap to scan systems yourself - just to see what’s out there or to test if your firewalls are woking, etc.
scrubbles@poptalk.scrubbles.tech 3 days ago
Uh sorry dude, but no this isn’t a script kiddy, these are bots that scan every IP address every day for any open ports, it’s a constant thing. If you have a public IP, you have people, govs, nefarious groups scanning it. AWS will tell you the same as if you were hosting it locally, close up the ports, put it on a private network. Use a vpc and WAF in AWS’ case.
I get scanned constantly. Every hour of every day dark forced attempt to penetrate our defences.
MightBeFluffy@pawb.social 3 days ago
Not on AWS and yes I know I can’t stop port scanning and bad traffic is a thing. Doesn’t stop me from filling out the form. I think to piss off you and the other commenters, I’ll write a script to auto fill out AWS abuse forms. Also script kiddy or bot, all the same to me, their hosting provider is getting a message from me
i_am_not_a_robot@discuss.tchncs.de 3 days ago
Port scanning isn’t abuse but automatically filing frivilous abuse reports is.
remotelove@lemmy.ca 3 days ago
Good luck with that, I suppose. Botnets can have thousands, if not hundreds of thousands of infected hosts that will endlessly scan everything on the interwebs. Many of those infected hosts are behind NAT’s and your abuse form would be the equivalent of reporting an entire region for a single scan.
But hey! Change the world, amirite?
Reggie@discuss.tchncs.de 2 days ago
I’ll write a script to auto fill out AWS abuse forms Sounds like you are the script kiddie here
scrubbles@poptalk.scrubbles.tech 3 days ago
I mean go for it? They literally can’t do anything, you might as well complain that fire is hot though. It’s part of being in the Internet. They provide safety gloves, via VPCs and fireballs, but if you choose not to use them then… yeah I mean youre probably gonna get burned
Randomgal@lemmy.ca 3 days ago
This is some cartoon-villain type unhinged behavior.
irmadlad@lemmy.world 3 days ago
Not on AWS and yes I know I can’t stop port scanning and bad traffic is a thing. Doesn’t stop me from filling out the form.
On occasion, if they end up in recidive, I’ll report them to AbuseIPdb. If I did it for all attempts, I’d be as busy as a squirrel in a nut factory, because the bots are thick out in the ether. Like every minute of the day they’re out there throwing rocks at the castle wall. I had to start logrotating because logs were getting so big it was difficult to review and audit. Every so once in a while, they’ll break out the trebuchet and lob something significant, but I’ve had no breaches to date.
My servers are single user only, so buttoning things down is a little less complicated for me.
uzay@infosec.pub 2 days ago
I think a lot of peope understandably misunderstand this post because it doesn’t really explain the situation. After reading OP’s comments I gather that OP put a new server onlibe (not on AWS) and was immediately port scanned by a host that is on AWS. Since OP did not consent to being port scanned, they filled out an abuse complaint with AWS, the hoster the scan came from, out of principle, knowing that it probably won’t do much. Which is totally fine if that is how you want to spend your time.
I think what most commenters thought is that OP was hosting with AWS and complained to them that someone else scanned their server. This does not seem to be the case.
dgdft@lemmy.world 2 days ago
Absolutely not — the issue here is OP knowingly submitting false abuse reports.
Port scans of public hosts are not considered abuse per the CFAA or Amazon’s AUP without other accompanying signs of malicious intent.
Amazon may take action against egregious mass-scanning offenders per the “…to violate the security, integrity, or availability of any user, network…” verbiage, especially if they’re fingerprinting services or engaging in more sophisticated recon, but OP’s complaints are nowhere near meeting that threshold.
cellardoor@lemmy.world 3 days ago
If I showed you my WAN-side firewall logs you’d have a panic attack. I have a /29 block and about 10 scans tap one IP or another every second. It’s part of being on the internet.
Your domestic home router experiences the exact same thing. Every moment of every day.
Will you report every scan? Every Chinese IP? Every US IP? It’s completely common place to have someone ‘knock on the door’.
Get off IPv4 anyway and onto IPv6. Good luck to them finding you by chance in there.
Clearwater@lemmy.world 3 days ago
I ran a Tor relay on one of my spare servers for a while, and my god did that thing get port scanned. Even two years after I stopped hosting the relay, it was still getting pinged every 5-10 seconds (while my other servers tend to get pinged “only” once ever 20-30 seconds).
cmnybo@discuss.tchncs.de 3 days ago
Switch to IPv6 only and the port scans will go away. The address space is so big that port scanning is difficult, so the usual bots don’t bother.
KairuByte@lemmy.dbzer0.com 3 days ago
Sure but there are just some things you can’t run over ipv6
darcmage@lemmy.dbzer0.com 3 days ago
Remember to also report ssh login attempts and unauthorized wordpress access (even if wordpress isn’t installed).
markstos@lemmy.world 3 days ago
Also, all spam messages.
MightBeFluffy@pawb.social 3 days ago
For SSH it will have to be attempted connections. Ain’t no way I’m putting a forward facing SSH. I’ll deal with any downtime that comes from not being able to access my server remotely
TwiddleTwaddle@lemmy.blahaj.zone 3 days ago
Trying to learn here, are these SSH login attempts on the root user? If not, is it just the firewall logs?
remon@ani.social 3 days ago
MightBeFluffy@pawb.social 3 days ago
The sad reality of the Internet. Being the first for this new server feels like a “Welcome to the Internet, glad you are here” kind of message
irmadlad@lemmy.world 3 days ago
I am reminded of a Richard Pryor skit in which he tells about a football player he knew who bit the fingers off of an opponent who was trying to gouge his eyes through his helmet. When Pryor asked him why he bit the guy’s fingers off he said ‘Everything outside the mask is his. Everything inside the mask is mine.’
Schwim@lemmy.zip 3 days ago
It wasn’t a script kiddy. It wasn’t even a human. You are going to be a very busy individual if you decide to report every port scan you find.
MightBeFluffy@pawb.social 3 days ago
That’s what automation is for
sugar_in_your_tea@sh.itjust.works 2 days ago
Or just close off the most common vectors, such as disabling root ssh login, doing key-only SSH auth, and block traffic from regions of the world you don’t need to support.