Live data from Hacker News

An Innovative Phishing Style

tehaurum.wordpress.com

11–20 of 83 posts

Re: An Innovative Phishing Style

#11
> As far as I could tell, the debugger trap was basically calling the debugger function if it detects a running debugger.

This is a fairly common trick, you just run the debugger method in a setTimeout loop since it's a no-op if the debugger isn't open. It's a common tactic used by quasi-illicit sport streaming websites that are usually filled with ads.

There's a button in Chrome Dev Tools to disable breaking on breakpoints that gets round this.

Re: An Innovative Phishing Style

#12
Wanna bet that if I call anybody working in a bank, telling them I am from the IT department and I want them to check the new login page (done the way described in this article), they will enter there their login & password?

Re: An Innovative Phishing Style

#14
post #10

This is hard to defend against, but changing the default colour scheme (also used for every window title bar) helps somewhat.

Not engaging in trading requests from strangers also works.

Although some are in it for the long game, my GF's son was scammed by a "friend" on Fortnite who spent at least two weeks befriending the guy.

Re: An Innovative Phishing Style

#15
I will vouch for the author of this article. Smart kid!

On a slightly off-topic, I think it's safe to say that trading and farming items in popular games, is responsible for cheaters, unfair practices, and in turn developers churning out more of these.

I hope we can return to games, where I pay for a title for its entertainment value, bar of all loopholes and caveats.

Re: An Innovative Phishing Style

#16
post #7
post #6

Browsers should implement some mechanisms to combat this type of phishing. I've gone ahead and reported this as a phishing site on Google safe browsing and other services.

You can just disable grouping taskbar items, which is convenient for me regardless of this issue. Then it's clear that 1 window is not 2 windows.

It's possible for programs to make windows that aren't in the taskbar though. I'm not entirely sure I would know/remember whether this ever happens for a browser.

Re: An Innovative Phishing Style

#17
Doesn't OAuth and similar work by redirecting you to the login page?

I don't recall ever seeing a version that opens a popup to get you to login. This would immediately raise my suspicions on this basis (popup windows can be controlled by the opening website to a large degree!).

Re: An Innovative Phishing Style

#18
post #17

Doesn't OAuth and similar work by redirecting you to the login page? I don't recall ever seeing a version that opens a popup to get you to login. This would immediately raise my suspicions on this basis (popup windows can be controlled by the opening website to a large degree!).

At most 10% of the target audience (and that's a generous upper bound) are going to have the deep understanding of web technologies that is required to make those deductions. And even if they do, not all of them are going to realize this in that particular moment. (For instance, it didn't immediately occur to me while reading the article.)

Re: An Innovative Phishing Style

#19

I will vouch for the author of this article. Smart kid! On a slightly off-topic, I think it's safe to say that trading and farming items in popular games, is responsible for cheaters, unfair practices, and in turn developers churning out more of these. I hope we can return to games, where I pay for a title for its entertainment value, bar of all loopholes and caveats.

It's a stretch to say it results in cheaters, people have been writing cheats since quakeworld.

Re: An Innovative Phishing Style

#20
post #6

Browsers should implement some mechanisms to combat this type of phishing. I've gone ahead and reported this as a phishing site on Google safe browsing and other services.

> Browsers should implement some mechanisms to combat this type of phishing.

combatting this doesn't require browsers - you can have a passwordless login mechanism (like email links!).

Or, if browsers do indeed want to combat issues such as these, we'd need support for client-side certs (so you can login using a key-pair!), rather than username/password.

Or, rely in a tool like lastpass to consistently enter the credentials (which, presumably, will check the domain first and if it doesn't match, won't let you put the credentials in).

Post reply on HN