Live data from Hacker News

Stopping phishing campaigns with Bash

blog.haschek.at

151–160 of 169 posts

Re: Stopping phishing campaigns with Bash

#151
That is really a good way to make them drop all the target. but rather if I were to do it I will do it with set of different signature snuffling randomly to make them un-filterable and limit the rate of submission such that they dont immediately notice me and I can make their database full of dummy data which makes it useless for them. Many times you can also get to execute arbitrary sql-injection and can delete the database.

In fact, in past when in collage I was trying to learn some hacking basics to find vulnerable servers. And as on the googled article like most scripting kiddies, I searched and found a vulnerable site which was already hacked and had installed shell.php on it. What that vulnerability did was, it found a way to inject the browser navigator name into php script using /proc/self/environ. after studying attack what I did was, remove the shell and patched the vulnerable file with some obfuscation. I was so naive(what would have happened if my IP was tracked and I became suspected criminal),now seeing past luckily I never got my self involved in legal things.

Re: Stopping phishing campaigns with Bash

#152
post #132

Earlier quoted context omitted.

> A more appropriate response is to report the abuse who manages the infrastructure (most likely a legitimate provider) and the domain registar; both usually have appropriate channels and response procedures just for that. Unless of course it's behind Cloudflare - then you cannot find out whose infrastructure the criminals are operating from and Cloudflare itself does not give a fuck. Best case scenario: they will fo…

They claim they will do all this for you if they are (allegedly) proxying malicious content. Source: their abuse form [1], selecting "Phishing & Malware". Did you have bad experiences with this? Might be worth sharing. [1] https://www.cloudflare.com/abuse/form

i used the form and emailed abuse@ (for sites blatantly impersonating relief effort organizations at the onset of covid-19)

all attempts got responses like "cool, but we don't do any of that. please contact google safe-site(tm) beta or something and get it blocked on the browser via that".

Everyone here posting that they replied probably used email from a domain that is an expensive paid customer from them. I used a @gmail one.

Re: Stopping phishing campaigns with Bash

#153
post #72

A friend of mine fell victim to a renting scam here in Czechia. The phishing site was using the native .cz TLD, which is well within the reach of Czech authorities. I was particularly bored that day so I went to a local police department to report a crime. I advised the policeman to take down the phishing site - it was actively facilitating a crime. The poor cops had no idea what to do and in the end they told me tha…

Probably whoever works at the desk there has no idea how to get in touch with the department responsible for investigating internet crimes. They're probably in another office far away, and never interact with each other.

Re: Stopping phishing campaigns with Bash

#155

Earlier quoted context omitted.

I like to think it helped out, but at the same time, these people are professionals and will have automation to generate new instances and scam campaigns easily. At least it should be more difficult for them to set up new bank accounts though, they need ID for that, and / or a network of mules, and those are finite resources.

I think the bank thing is done through students quite often: "Hey, I can't get a bank account as I'm a refugee fleeing a war, please help by receiving £5000 cash, we'll give you £100. Say it's a gift from your Aunty to buy a car with." I've seen reports of this in the UK at least, maybe they managed to stop it.

At least in the US the people who accept the offer can be charged as money mules.

Re: Stopping phishing campaigns with Bash

#156
post #85

Earlier quoted context omitted.

So like... Backups? Restore, put it behind basic auth and email the password to the members active in the past few weeks, then at your leasure implement some captchas and go from there. Heck, restore the forum publicly as well and use that as a sandbox to see how they'll bypass it.

He said DDoS which has nothing to do with the data itself, and auth/captcha won't help. You'll have to upgrade to beefier servers, fatter pipes, or pay for a reverse proxy.. CF is free now and kinda helps sometimes, but it wasn't in the past, and any hacker with a grudge can take down your site anyway. It's about forcing you to spend money; which, if you're a hobby site forum host, you probably don't have.

Ah, right, I read it differently but I think you're right. In my initial understanding the spammers hit back by a huge spam wave, but a counter DDoS could also be.

Re: Stopping phishing campaigns with Bash

#157
I've done stuff like this but behind Tor. I tried to make the data random enough it would be tough to see which records were real. I remember once my IP was getting blocked after a certain amount of requests (not sure if via some automated fail2ban or a human) but Tor has an API to swap to a new outbound IP, so I just had it do that in the case of a timeout.

Re: Stopping phishing campaigns with Bash

#158
post #108
post #106

Earlier quoted context omitted.

> "Always remember that U.S. courts are courts of law, not courts of justice. That's usually a good thing (less left to interpretation)" Are they? My impression is that US courts rely heavily on the whims of a jury and the judge, leading to very different outcomes for similar cases. Though often leading to injustice (heavy punishments for poor and/or black people, light punishments for rich and/or white people) rathe…

I think their biases would have worse consequences if their goal was following some intuitive gut feeling of justice rather than having a goal of applying the law even when the law is known to be imperfect. That is, the less explicit the rules are, the more wiggle room there is for bias to act.

I'm not so sure, I feel the civil law system followed in continental Europe works much better as it's based on the spirit of the law instead of the exact letter and comma.

Hard to say if this would be a better fit for the US though -- I've no idea if that's causing issues elsewhere in more corrupt societies or not.

Re: Stopping phishing campaigns with Bash

#159

Earlier quoted context omitted.

This can be classified as denial of service attack because of the rate your are sending the requests. Depends on the law (and on the interpretation as well). I doubt that the phising guys behind this will file a complaint though.

To poison some phishing data you don't need to overload any server. Although the act itself of poisoning data could be seen as a DoS but since the service in question is an illegal one IANAL but I don't think it would stand in court.

It is very important to understand this from the legal stand point. If you overload a legitimate or illegitimate service you might commit a crime (depending on the country). I can give you a simple example of this in a different context. In our country you cannot go after the criminal who committed the crime and cannot cause them harm. Few years back a lady got robbed by two guys on a motorbike and she went after them and hit the motorbike with her car. She was prosecuted for assault. This is a very similar situation here. Again, depending on your country, state etc. this _might_ be a bad idea.

Re: Stopping phishing campaigns with Bash

#160

All banks in the EU are required to use 2FA, I'm curious how these hackers get around that.

For quite a long time my bank used cargo culted 2FA i.e. 2x things that you know. Pretty embarrassing really. Thankfully they now have a card reader device but it's only used for certain actions (like adding new payees).

In the EU? That definitely wouldn't be compliant, unless we're talking about 90s or something.
Post reply on HN