Skip to content

feat(mailoney): support next JSONL format with malwaredir storage#17

Open
t3chn0m4g3 wants to merge 1 commit into
masterfrom
mailoney
Open

feat(mailoney): support next JSONL format with malwaredir storage#17
t3chn0m4g3 wants to merge 1 commit into
masterfrom
mailoney

Conversation

@t3chn0m4g3

Copy link
Copy Markdown
Member

@trixam @elivlo - Please review and test.

Summary

  • add support for the upcoming Mailoney next version JSONL event format
  • switch Mailoney config examples from legacy commands.log to log/log.json
  • use [MAILONEY] malwaredir for Mailoney stored .eml files and attachments
  • preserve non-rate-limit Mailoney JSON fields as EWS AdditionalData
  • send stored mails/attachments only when send_malware = true

Mailoney Reference

This targets the new Mailoney version currently available on the next branch:
https://github.com/t3chn0m4g3/mailoney/tree/next

That version replaces the old command-style log with flat JSONL events for
mail, auth, session, and rate_limit_block, and stores captured mail data
under its configured storage directory.

Tests

  • python3 -m compileall honeypots/mailoney.py modules/ealert.py
  • python3 -m unittest discover -s tests

Update Mailoney parsing for the new JSONL event schema, skip rate-limit
events, preserve event fields as additional data, and attach stored .eml
files/attachments only when send_malware is enabled.

Also switch example configs to log/log.json and Mailoney's storage path via
malwaredir, plus add focused unit coverage for the new behavior.
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.

3 participants