ABUSE.MOM
THREAT REPORT

IP Threat Report
31.13.115.28

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 09:02:28
First seen: 2026-03-07 04:00:07
Last seen: 2026-03-07 04:00:07
80

⛔ Verdict: BLOCK

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

BURSTREFERER
01

Geolocation & Classification

IP Address
31.13.115.28
Type
Residential
Country
🇸🇪 Sweden
City
Luleå
ISP
Facebook, Inc.
Organization
Meta Platforms Ireland Limited
Autonomous System
AS32934 Facebook, Inc.
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 25 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 31 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 80
03

Observed Activity

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

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

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

04

Timeline

2026-03-07 04:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 25 req / 2s (+35), Burst: 31 req / 10s (+35), Foreign referer seen (+10)
2026-03-07 04:00:07
Last malicious request observed
Total score reached: 80/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Facebook, Inc.
AS32934 · 🇸🇪 Sweden
06

Recommendations

Actions taken & recommended

  • IP 31.13.115.28 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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 31.13.115.28.

09

Blacklist Status (DNSBL)

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

✓ Clean
Spamhaus ZEN

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

10

Threat Analysis

31.13.115.28 has been assigned a threat score of 80/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 31.13.115.28, geolocated to Luleå, Sweden, operating on the network of Facebook, Inc., as a source of suspicious network activity. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. The score of 80/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇸🇪 Top threats from Sweden

View all →

🏢 Same network: AS32934

31.13.127.87 (135)31.13.127.41 (135)31.13.127.18 (135)57.141.0.35 (110)57.141.0.48 (90)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 Responsible Disclosure Ethics

Responsible disclosure balances public safety with giving vendors time to patch vulnerabilities. The security community generally supports coordinated disclosure timelines, but disagreements about appropriate timeframes and full disclosure continue to drive policy debates.

🔍 Check Any IP Address

Share this report: