evilginx2 icon indicating copy to clipboard operation
evilginx2 copied to clipboard

[New Feature] Add Notifications for Events per Phishlet Using `notify`

Open DrorDvash opened this issue 10 months ago • 6 comments

Summary

A small PR for notify integration, allowing you to track real-time events by sending notifications for:

  • Captured Username
  • Captured Password
  • Captured Session (Cookies/Tokens)

There are more PRs offering notifications, so there is nothing new here, i just love that notify is a wrapper to a variety of supported platforms and makes it easy to configure.

Note: This includes a previous PR i've made - https://github.com/kgretzky/evilginx2/pull/1115 Set Custom User-Agent.

Features

  • ✅ Send notifications using the notify CLI tool.
  • ✅ Any method supported by notify tool - Slack / Discord / Telegram / Teams / Webhook / Email / Pushover / ...
  • ✅ Enable/Disable notifications per phishlet.
  • ✅ Option to show/hide the captured data in the notification

Requirements

  1. Install notify and make sure it's in your $PATH
    go install -v github.com/projectdiscovery/notify/cmd/notify@latest
    
  2. Create and configure your provider-config.yaml. You can choose 1 or more provider. For example, here i chose Discord and Webhook image

Usage

  1. Enable notifications for a phishlet via:
    phishlets notify <phishlet> <off|on|minimal>
    
  • on - includes sensitive details - will send the username, password and session in clear-text
  • minimal - send only the event title, if you want to avoid sending victim details.

Screenshots

image image

minimal mode (no sensitive data) image

TODO

Support more events

DrorDvash avatar Feb 03 '25 16:02 DrorDvash

why this error?

Failed to send notification: exit status 1

M3d-Edge avatar Apr 18 '25 01:04 M3d-Edge

why this error?

Failed to send notification: exit status 1

Please add more context.

  • Did you follow all the steps?
  • Did you create and configure your provider-config.yaml?
  • Did you make sure notify is in your PATH?

You can do a simple check in your terminal: echo test | notify if it failed and you didn't get a notification, your problem is within the notify tool. You can follow the steps in the original notify repo to make sure everything is configured properly.

DrorDvash avatar Apr 18 '25 04:04 DrorDvash

why this error? Failed to send notification: exit status 1

Please add more context.

  • Did you follow all the steps?
  • Did you create and configure your provider-config.yaml?
  • Did you make sure notify is in your PATH?

You can do a simple check in your terminal: echo test | notify if it failed and you didn't get a notification, your problem is within the notify tool. You can follow the steps in the original notify repo to make sure everything is configured properly.

Thanks now its work config was not on correct path C:\Users\XXX.config\notify

M3d-Edge avatar Apr 18 '25 12:04 M3d-Edge

Hi, after testing got annoying alerts notification that flood my telegrambot my phishlet has alot of

[0] detected authorization URL - tokens intercepted:

so every detected authorization URL it will sent notification, if phishlet detected 50 authorization URL will recieve 50 alerts notification on my telegram which is very annoying if you have solution for this could be great thanks

M3d-Edge avatar Apr 18 '25 13:04 M3d-Edge

Please which PATH to add the provider-config.yaml?

AnonyMousSKYsWORLD avatar Jul 21 '25 11:07 AnonyMousSKYsWORLD

Please which PATH to add the provider-config.yaml?

https://github.com/projectdiscovery/notify?tab=readme-ov-file#provider-config

DrorDvash avatar Jul 27 '25 18:07 DrorDvash