Got my first script kiddy
-
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.
-
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?
-
You contacted Amazon over a port scan?
Yes. Don't port scan my shit.
-
Yes. Don't port scan my shit.
wrote last edited by [email protected]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.
Edit: also, I think "script kiddy" is a bit of a stretch here.
-
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.
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.'
-
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.
Edit: also, I think "script kiddy" is a bit of a stretch here.
wrote last edited by [email protected]I don't have any open ports. I do not care if I did. Port scanning is not authorized traffic.
I would love to see the support request from AWS for this.
Here you go:
Mandiant ASM scanners perform a variety of security-related data-gathering tasks, all intended to positively identify assets and their security posture. The gathered information is analyzed by our research team and proactively published to the owners of this information through our freemium product. No Collection task performed requires authorized access. It is intentionally designed to be light. While your IDS or WAF may have alerted on these scans, these are benign flags and are not indicative of malicious behavior.
If you have further questions, or would like to opt-out, please reply to this message and you will be routed to the appropriate team.
-
I don't have any open ports. I do not care if I did. Port scanning is not authorized traffic.
I would love to see the support request from AWS for this.
Here you go:
Mandiant ASM scanners perform a variety of security-related data-gathering tasks, all intended to positively identify assets and their security posture. The gathered information is analyzed by our research team and proactively published to the owners of this information through our freemium product. No Collection task performed requires authorized access. It is intentionally designed to be light. While your IDS or WAF may have alerted on these scans, these are benign flags and are not indicative of malicious behavior.
If you have further questions, or would like to opt-out, please reply to this message and you will be routed to the appropriate team.
port scanning is not authorized traffic
Hahahahahaha
And?
-
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.
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.
-
I don't have any open ports. I do not care if I did. Port scanning is not authorized traffic.
I would love to see the support request from AWS for this.
Here you go:
Mandiant ASM scanners perform a variety of security-related data-gathering tasks, all intended to positively identify assets and their security posture. The gathered information is analyzed by our research team and proactively published to the owners of this information through our freemium product. No Collection task performed requires authorized access. It is intentionally designed to be light. While your IDS or WAF may have alerted on these scans, these are benign flags and are not indicative of malicious behavior.
If you have further questions, or would like to opt-out, please reply to this message and you will be routed to the appropriate team.
Port scanning is not authorized traffic.
Lol what
I think you should read the terms of your AWS contract. How do you think aws moves instances if not for agents gathering metrics?
And this case is Mandiant, so you're fine.
Are you sure you're ready for AWS?
-
Port scanning is not authorized traffic.
Lol what
I think you should read the terms of your AWS contract. How do you think aws moves instances if not for agents gathering metrics?
And this case is Mandiant, so you're fine.
Are you sure you're ready for AWS?
Not on AWS
-
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.
Remember to also report ssh login attempts and unauthorized wordpress access (even if wordpress isn't installed).
-
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.
Haha, I get one of those every other day.
-
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.
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.
-
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.
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
-
port scanning is not authorized traffic
Hahahahahaha
And?
And abuse forms get filled out
-
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.
That's what automation is for
-
Remember to also report ssh login attempts and unauthorized wordpress access (even if wordpress isn't installed).
Also, all spam messages.
-
Haha, I get one of those every other day.
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
-
Remember to also report ssh login attempts and unauthorized wordpress access (even if wordpress isn't installed).
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
-
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
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.
