ABUSE.MOM
THREAT REPORT

IP Threat Report
4.154.76.16

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:59:19
First seen: 2026-07-03 20:01:37
Last seen: 2026-07-05 03:52:15
178

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 178/100. Total malicious requests observed: 134.

DANGER_PATHMETHODRATIO_404REFERERUA_CHANGED
01

Geolocation & Classification

IP Address
4.154.76.16
Type
Hosting
Country
🇺🇸 United States
City
Quincy
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (westus2)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
134
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 213
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-07-03 20:01:37
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 1 (+10), Danger medium hits: 2 (+20)
2026-07-05 03:52:15
Last malicious request observed
Total score reached: 178/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 4.154.76.16 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 4.154.76.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

IP 4.154.76.16 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🤖 Bot Detection

Address UA spoofing from 4.154.76.16: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 4.154.76.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de
✓ Clean
bl.spamcop.net
✓ Clean
b.barracudacentral.org

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

4.154.76.16 has been assigned a threat score of 178/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

Network traffic from 4.154.76.16, located in Quincy, United States, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 134 hostile requests from this IP — roughly 134 per day on average. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 120 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 178/100 places this address in the top tier of severity. Block and investigate any historical connections.

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.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)103.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS8075

20.226.81.88 (280)20.48.26.146 (280)191.234.169.57 (280)52.237.113.70 (280)104.208.65.18 (280)View all →
12

Security Intelligence

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

💡 Deception Technology Beyond Honeypots

Modern deception technology deploys fake credentials, decoy files, and breadcrumbs throughout production environments. When attackers interact with these deceptions, high-fidelity alerts trigger with virtually zero false positives.

🔍 Check Any IP Address

Share this report: