AI-powered phishing detection system with real-time email and URL analysis. Built for Microsoft Imagine Cup 2026 using Azure AI Services, ML models, and browser extension.
PhishGuard AI is an intelligent cybersecurity solution that detects and prevents phishing attacks through:
- Real-time Email Analysis: Scans incoming emails for phishing indicators
- URL Analysis: Evaluates links for malicious content
- Machine Learning Models: Trained on phishing email datasets for accurate detection
- Azure AI Integration: Leverages Azure Cognitive Services for advanced threat analysis
- Browser Extension: Instant alerts and warnings for suspicious emails/URLs
- Web Dashboard: Centralized monitoring and threat tracking
- Frontend: HTML5, CSS3, JavaScript (Web App + Browser Extension)
- Backend: Node.js with Express.js, Python for data processing
- Cloud: Microsoft Azure (Cognitive Services, App Service, Storage)
- ML/AI: Python (scikit-learn, TensorFlow), Azure ML
- Database: Azure SQL Database / MongoDB
- APIs: Azure Text Analytics, Content Moderator, Anomaly Detector
- DevOps: GitHub Actions, Docker (optional)
PhishGuard-AI-ImagineCup2026/
βββ src/
β βββ data_processing/ # Python ML pipeline
β β βββ __init__.py
β β βββ email_analyzer.py # Email feature extraction
β β βββ url_analyzer.py # URL analysis module
β β βββ model_trainer.py # Model training pipeline
β βββ backend/ # Node.js backend
β β βββ server.js
β β βββ routes/
β β βββ middleware/
β βββ extension/ # Browser extension
β βββ manifest.json
β βββ popup.html
β βββ content.js
βββ models/ # Trained ML models
βββ app.js # Main application
βββ index.html # Web dashboard UI
βββ styles.css # UI styling
βββ requirements.txt # Python dependencies
βββ package.json # Node.js dependencies (TODO)
βββ .env.example # Environment variables template
βββ .gitignore
βββ LICENSE
βββ README.md
- Node.js 14+ and npm
- Python 3.8+
- Azure account with subscription
- Git
-
Clone the repository
git clone https://github.com/Chetan-code-lrca/PhishGuard-AI-ImagineCup2026.git cd PhishGuard-AI-ImagineCup2026 -
Set up environment variables
cp .env.example .env # Edit .env with your Azure credentials and API keys -
Install Python dependencies
pip install -r requirements.txt
-
Install Node.js dependencies (TODO)
npm install
-
Run the application
node app.js
Visit
http://localhost:3000
| Name | Role | Responsibility |
|---|---|---|
| Chetan | Team Lead | Project coordination, Backend development |
| Srikanth | ML Engineer | Model training, Data processing pipeline |
| Nandhitha | Frontend Developer | UI/UX design, Web dashboard |
| Sreelaxmi | Cloud Engineer | Azure setup, API integration, DevOps |
- Repository setup & team onboarding
- Azure resources provisioning
- Dataset collection & preprocessing
- Environment configuration
- Email analyzer module
- URL analyzer module
- ML model training & evaluation
- Backend API development
- Web dashboard UI
- Browser extension development
- Azure service integration
- Real-time alert system
- Unit & integration testing
- Security audits
- Performance optimization
- Azure deployment (App Service)
- Final documentation
β Real-time Detection: Analyzes emails/URLs as they arrive β ML-Powered: Trained models with 95%+ accuracy β Azure Integration: Enterprise-grade cloud infrastructure β User-Friendly: Simple dashboard and browser extension β Scalable: Designed for enterprise deployment β Privacy-Focused: Local analysis, encrypted data transmission
- Go to the Issues tab
- Click New Issue
- Use templates: Bug, Feature, Enhancement
- Assign to team member & add labels
- Create feature branch:
git checkout -b feature/your-feature - Commit changes:
git commit -m "Feature: description" - Push & create PR:
git push origin feature/your-feature - Request code review from team members
- Merge after approval
- JavaScript: ESLint configuration (upcoming)
- Python: PEP 8 compliance
- Commit messages: Descriptive, past tense
- Branch naming:
feature/,bugfix/,docs/prefixes
- Azure Cognitive Services Docs
- Phishing Email Dataset (Kaggle)
- OWASP Phishing Prevention
- Google Imagine Cup Guidelines
- Never commit
.envfiles with real credentials - Use Azure Key Vault for secrets management
- Implement HTTPS for all communications
- Validate & sanitize all user inputs
- Regular security audits & updates
- GDPR compliance for data processing
MIT License - See LICENSE file for details
Contributions welcome! Please:
- Fork the repository
- Create a feature branch
- Make your changes
- Submit a pull request with description
For questions or issues:
- Create a GitHub Issue
- Contact: [Team Email] (TODO)
- Discord: [Link] (TODO)
Last Updated: November 18, 2025 Status: In Development for Microsoft Imagine Cup 2026