[1] https://secureannex.com/blog/cyberhaven-extension-compromise.... [2] https://secureannex.com/blog/sclpfybn-moneitization-scheme/ (referenced in the article)
8M users' AI conversations sold for profit by "privacy" extensions
31–40 of 261 posts
Re: 8M users' AI conversations sold for profit by "privacy" extensions
#32Earlier quoted context omitted.
Let's say we don't trust ublock. At the very least it is still blocking ad networks which do reduce internet performance and are vectors of exploitation, so it is still adding value whether you trust it or not.
Under the hypothetical that we don't trust ublock, it would be foolish to grant it full access to all data on all websites. It would not be adding value.
Re: 8M users' AI conversations sold for profit by "privacy" extensions
#33Re: 8M users' AI conversations sold for profit by "privacy" extensions
#34The company behind this appears to be "real" and incorporated in Delaware. > Urban Cyber Security INC https://opencorporates.com/companies/us_de/5136044 https://www.urbancybersec.com/about-us/ I found two addresses: > 1007 North Orange Street 4th floor Wilmington, DE 19801 US > 510 5th Ave 3rd floor New York, NY 10036 United States and even a phone number: +1 917-690-8380 https://www.manhattan-nyc.com/businesses/urba…
If that looks use-italics "really legitimate" to you, then you might be easily scammed. I'm not saying they're not legitimate, but nothing that you shared is a strong signal of legitimacy.
It would take a perhaps a few hundred dollars a month to maintain a business that looked exactly like this, and maybe a couple thousand to buy one that somebody else had aged ahead of time. You wouldn't have to have any actual operations. Just continuously filed corporate papers, a simple brochure website, and a couple virtual office accounts in places so dense that people don't know the virtual address sites by heart.
Old advice, but be careful believing what you encounter on the internet!
Re: 8M users' AI conversations sold for profit by "privacy" extensions
#35The company behind this appears to be "real" and incorporated in Delaware. > Urban Cyber Security INC https://opencorporates.com/companies/us_de/5136044 https://www.urbancybersec.com/about-us/ I found two addresses: > 1007 North Orange Street 4th floor Wilmington, DE 19801 US > 510 5th Ave 3rd floor New York, NY 10036 United States and even a phone number: +1 917-690-8380 https://www.manhattan-nyc.com/businesses/urba…
1000 N. WEST ST. STE. 1501, WILMINGTON, New Castle, DE, 19801
It almost matches this law firms address but not quite.
https://www.skjlaw.com/contact-us/
Brandywine Building 1000 N. West Street, Suite 1501 Wilmington DE 19801
Re: 8M users' AI conversations sold for profit by "privacy" extensions
#36I thought manifest v3 was supposed to make chrome extensions secure?
Re: 8M users' AI conversations sold for profit by "privacy" extensions
#37Deleted.
There are honest ways to make a living. In this case honest is “being transparent” about the way data is handled instead of using newspeak.
Re: 8M users' AI conversations sold for profit by "privacy" extensions
#38So much of what's aimed at nontechnical consumers these days is full of dishonesty and abuse. Microsoft kinda turned Windows into something like this, you need OneDrive "for your protection", new telemetry and ads with every update, etc. In much of the physical world thankfully there's laws and pretty-effective enforcement against people clubbing you on the head and taking your stuff, retail stores selling fake produ…
I spend a lot of time trying to think of concrete ways to improve the situation, and would love to hear people's ideas. Instinctively I tend to agree it largely comes down to treating your users like human beings.
Re: 8M users' AI conversations sold for profit by "privacy" extensions
#39Is the use of WebAssembly going to make spotting these malicious extensions harder?
Probably not. All side effects need to go through the js side. So you can alway see where http calls are made
That can be circumnavigated by bundling the conversations into one POST to an API endpoint, along with a few hundred calls to several dummy endpoints to muddy the waters. Bonus points if you can make it look like an normal-passing update script.
It'll still show up in the end, but at this point your main goal is to delay the discovery as much as you can.