Skip to content
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

Make ID Parameter configurable #4

Open
er4z0r opened this issue Apr 10, 2024 · 0 comments · May be fixed by #10
Open

Make ID Parameter configurable #4

er4z0r opened this issue Apr 10, 2024 · 0 comments · May be fixed by #10

Comments

@er4z0r
Copy link

er4z0r commented Apr 10, 2024

As a red teamer I am running a modified version of Gophish where I removed some the indicators that will give gophish away either by leaking information in the e-mails or the webserver responses. One of these modifications was to rename the rid parameter to something more common like utmid. I did this in models/campaign.go in the gophish source.

// RecipientParameter is the URL parameter that points to the result ID for a recipient.
const RecipientParameter = "utmid"

One consequence of this however was that the parameter does not show up as id but as utmid as part of the webhook payload:

DEBU[0032] {"campaign_id":103,"email":"[email protected]","time":"2024-04-09T20:19:40.927020587Z","message":"Clicked Link","details":"{\"payload\":{\"utmid\":[\"u06rVPK\"]},...

Since gophish-notifier expected the name to be id it did not pick up the field in the payload, which then makes it harder to search for the result in Gophish (especially in bigger campaigns).

I realize that this is totally on me. OTOH, I might not be the only one customizing this aspect of Gophish so it might be useful to make the name of this field configurable in gophish-notifier.

@er4z0r er4z0r linked a pull request Sep 4, 2024 that will close this issue
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 a pull request may close this issue.

1 participant