Potential Malicious IP on "Warning List of known Microsoft Azure Datacenter IP Ranges"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 650
- Forks
- 195
- Avg merge
- 18h 17m
- Merged PRs (30d)
- 74
Description
Hi All,
We used the warning list of "Microsoft Azure Datacenter IP Ranges" but we are facing to different IP with massive inbound scan activity.
We kindly ask to evaluate to divide the list considering apart from Indian IP.
In particular we received scan event from:
- 4.224.240.93 --> 4.224.0.0/13
- 40.80.93.32 -->40.80.64.0/19
- 20.219.155.180 -->20.218.0.0/15
Alternatively, is it possible to consider excluding these subnets from the waning list?.
Thanks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the warning list for “Microsoft Azure Datacenter IP Ranges” and reviewing how the listed subnets are represented. Check the three reported ranges and the request to separate or exclude them, then verify that the resulting list matches the intended policy without unintended coverage changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100