-
Notifications
You must be signed in to change notification settings - Fork 45
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
Update the shady-links rule to match IPs #303
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good find! Any chance we can add a unit test for this?
""" | ||
|
||
# ruleid: shady-links | ||
req = urllib3.Request("https://[email protected]", headers={"User-Agent": os}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
did you want to add a "simple" test? e.g. https://1.3.4.5/foo.exe
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://faker.readthedocs.io/en/master/providers/faker.providers.internet.html#faker.providers.internet.Provider.ipv4
helps too, but might be overkill :D
The
shady-links
rule try to match suspicious URLs. However, it's not looking for IPs although those are more discrete means to reach C2 instances. This PR add support to detect IPv4 & IPv6