# Phishing site on ipfs.io

**URL:** <https://discuss.ipfs.tech/t/phishing-site-on-ipfs-io/14853>\
**Category:** Uncategorized\
**Tags:** security\
**Created:** [July 27, 2022, 10:18am UTC](https://discuss.ipfs.tech/t/phishing-site-on-ipfs-io/14853 "2022-07-27T10:18:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![anderscollstrup](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/anderscollstrup/32/6757_2.png) [@anderscollstrup](https://discuss.ipfs.tech/u/anderscollstrup)\
**Post date:** [July 27, 2022, 10:18am UTC](https://discuss.ipfs.tech/t/phishing-site-on-ipfs-io/14853/1 "2022-07-27T10:18:40Z")

</div>

Are ipfs aware of the phishing site its hosting?

[https://ipfs.io/ipfs/QmQLL5CwvUfkJTodMFie4QYhQC8n4cvg7ChJLR2KThz8xX/#ruc@ruc.dk](https://ipfs.io/ipfs/QmQLL5CwvUfkJTodMFie4QYhQC8n4cvg7ChJLR2KThz8xX/#ruc@ruc.dk)

It would be nice if the [abuse@ipfs.io](mailto:abuse@ipfs.io) mail was working or if there was some contact info on the website.

I hope it will removed soon

Regards Anders

---

<div class="post-metadata">

**Author:** ![Galactus](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/galactus/32/6540_2.png) [@Galactus](https://discuss.ipfs.tech/u/Galactus)\
**Post date:** [July 29, 2022, 5:48am UTC](https://discuss.ipfs.tech/t/phishing-site-on-ipfs-io/14853/2 "2022-07-29T05:48:23Z")

</div>

Refer the following thread for the same complaint. Pretty explained.

> [@How to block perticular cid](https://discuss.ipfs.tech/t/how-to-block-perticular-cid/14614):
>
> I just got phishing attack report on my public gateway. The concern cid is bafkreicimxxtvbx7l5isvw6vwn5mmkb6tjvspml72dd4vla67x3wbzvlhi How can I block particular cids to comply with takedown reports? Is there any centralized crowd maintained list of verified cids to autoblock them ipfs-wide? What is ipfs doing to reduce such phishing attacks from ipfs network? The attack reporter might have submitted the web url to various antivirus programs. Because of this, some of them are now rep…

> [@anderscollstrup](#):
>
> It would be nice if the [abuse@ipfs.io](mailto:abuse@ipfs.io) mail was working

That will only be useful for [ipfs.io](http://ipfs.io) admins to block the cid on their gateway only. The page still be accessible from other gateways.

---

<div class="post-metadata">

**Author:** ![anderscollstrup](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/anderscollstrup/32/6757_2.png) [@anderscollstrup](https://discuss.ipfs.tech/u/anderscollstrup)\
**Post date:** [July 29, 2022, 9:25am UTC](https://discuss.ipfs.tech/t/phishing-site-on-ipfs-io/14853/3 "2022-07-29T09:25:08Z")

</div>

Thanks, I was not aware that ipfs is peer network (I did not hear about it before my phishing case), that makes it hard to find out who actually host the phishing site :-/

I guess the best I can then is to block the entire [ipfx.io](http://ipfx.io) network in the firewall :-/  
But that will only protect onprem users.

/Anders

---

<div class="post-metadata">

**Author:** ![Galactus](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/galactus/32/6540_2.png) [@Galactus](https://discuss.ipfs.tech/u/Galactus)\
**Post date:** [July 29, 2022, 1:37pm UTC](https://discuss.ipfs.tech/t/phishing-site-on-ipfs-io/14853/4 "2022-07-29T13:37:23Z")

</div>

Rather, I would suggest to block the path rather than whole service.  
IPFS is good service. But just because of some nasty users, we should not expel the whole IPFS network.

---

<div class="post-metadata">

**Author:** ![ozzyjr](https://avatars.discourse-cdn.com/v4/letter/o/aeb1de/32.png) [@ozzyjr](https://discuss.ipfs.tech/u/ozzyjr)\
**Post date:** [June 16, 2023, 1:29pm UTC](https://discuss.ipfs.tech/t/phishing-site-on-ipfs-io/14853/5 "2023-06-16T13:29:31Z")

</div>

Bu on the other hand ipfs needs to figure some workaround to this problem, cuz links are changing on each phishing mail which is pretty annoying and forcing security people to block whole domain even if they don’t really want.