search

mitchellkrogza / Phishing.Database

Phishing Domains, urls websites and threats database. We use the PyFunceble testing tool to validate the status of all known Phishing domains and provide stats to reveal how many unique domains used for Phishing are still active.
MIT License
1.14k stars 257 forks source link

Dead Repo? - Lists No Longer Updating #899

Open 00011100 opened 4 months ago

00011100 commented 4 months ago

Describe the bug Many of the phishing links have not been updated in months. Is this project no longer being maintained? I'm surely not alone when I say I appreciate all of the hard work over the years, but I'm curious about the project's current state and if there are plans to keep things going. (Hoping so!)

spirillen commented 4 months ago

Hi, thanks for the question. You are not the first one to ask a similar question. their is this related issue in https://github.com/mitchellkrogza/Phishing and we are still crossing our fingers for answers, as we do spend a lot of time keeping the source actively maintained. Not at least with a big thanks to @g0d33p3rsec for all his contributions

GitHub
GitHub - mitchellkrogza/phishing: Central Repository for Adding Domains / Links to the Phishing.Database project - https://github.com/mitchellkrogza/Phishing.Database/
Central Repository for Adding Domains / Links to the Phishing.Database project - https://github.com/mitchellkrogza/Phishing.Database/ - mitchellkrogza/phishing
funilrys commented 4 months ago

The project is maintained. But our automation is broken. I've been working on it.

-- But as in everything in OSS, it's free time. So it might take more time.

g0d33p3rsec commented 4 months ago

I was going back over the history this morning to try to date the change that is causing the issue. The last submission of mine that I can find offhand that properly made it's way from the repo used for adding links to here was https://github.com/mitchellkrogza/phishing/pull/343 which was made on March 17. image

g0d33p3rsec commented 4 months ago

The project is maintained. But our automation is broken. I've been working on it.

-- But as in everything in OSS, it's free time. So it might take more time.

It looks like this repo was reset with 74f4cb0dfb8d1a467d8db9c5d12a0eba339e8c61 so I'm having some trouble tracing changes to the workflow back to the date that it was last known to properly work. I can see in travis-commit.sh where the false positive list is updated from the other repo https://github.com/mitchellkrogza/Phishing.Database/blob/a71846ff8054ad65793501c8276b0c6a886736bf/scripts/travis-commit.sh#L15 but I'm failing to find where new positive results are imported. @funilrys am I missing a call somewhere? I'm trying to understand the automation that takes place after a PR is merged into https://github.com/mitchellkrogza/phishing and the entry being added to the related list within this repo to try and test locally.

GitHub
GitHub - mitchellkrogza/phishing: Central Repository for Adding Domains / Links to the Phishing.Database project - https://github.com/mitchellkrogza/Phishing.Database/
Central Repository for Adding Domains / Links to the Phishing.Database project - https://github.com/mitchellkrogza/Phishing.Database/ - mitchellkrogza/phishing