IP Threat Report
4.223.76.100
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 52 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 364 | Medium-risk: admin panels, config files | +60 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 42 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 149 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 362 | Medium-risk: admin panels, config files | +60 | |
| Burst: 44 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 130 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 368 | Medium-risk: admin panels, config files | +60 | |
| Burst: 49 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 162 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 46 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 300 | Medium-risk: admin panels, config files | +60 | |
| Burst: 58 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 200 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 9 | Medium-risk: admin panels, config files | +60 | |
| Burst: 11 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 11 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 50 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 158 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 59 | Medium-risk: admin panels, config files | +60 | |
| Burst: 85 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 54 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 165 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 65 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 54 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 521 | Medium-risk: admin panels, config files | +60 | |
| Burst: 61 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 66 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 400 | Medium-risk: admin panels, config files | +60 | |
| Burst: 197 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 402 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 71 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 72 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 38 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 55 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 184 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 55 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 46 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 146 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 404 | Medium-risk: admin panels, config files | +60 | |
| Burst: 57 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 193 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 70 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 603 | Medium-risk: admin panels, config files | +60 | |
| Burst: 56 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 352 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 43 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 68 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 32 | Medium-risk: admin panels, config files | +60 | |
| Burst: 44 req / 10s | Abnormally fast request rate — automated scanning | +35 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 4.223.76.100 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🤖 Bot Detection
Address UA spoofing from 4.223.76.100: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🔎 Directory Scan Defense
IP 4.223.76.100 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Traffic Flood Defense
IP 4.223.76.100 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
4.223.76.100 has been assigned a threat score of 280/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
Threat intelligence analysis has linked 4.223.76.100 to malicious activity originating from Gävle, Sweden, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. During its 17-day observation window, we recorded 30 hostile requests from this IP — roughly 1.8 per day on average. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Sweden currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 280/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.
Related Threats
Security Intelligence
💡 TLS Fingerprinting (JA3/JA4)
TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.
💡 Memory Safety and Buffer Overflows
Buffer overflow vulnerabilities remain relevant in C/C++ applications despite decades of mitigation efforts. Modern protections like ASLR, stack canaries, and DEP reduce exploitability but determined attackers continue finding bypass techniques.