Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

DrorDvash
Copy link

@DrorDvash DrorDvash commented Feb 3, 2025

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 - #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

@M3d-Edge
Copy link

why this error?

Failed to send notification: exit status 1

@DrorDvash
Copy link
Author

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.

@M3d-Edge
Copy link

M3d-Edge commented Apr 18, 2025

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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants