ABUSE.MOM
THREAT REPORT

IP Threat Report
198.44.129.3

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 02:02:56
First seen: 2026-08-21 05:19:48
Last seen: 2026-08-23 02:02:18
60

⛔ Verdict: BLOCK

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

DANGER_PATH
01

Geolocation & Classification

IP Address
198.44.129.3
Type
Hosting
Country
🇺🇸 United States
City
Los Angeles
ISP
tzulo, inc.
Organization
Bao, DeYong
Autonomous System
AS11878 tzulo, inc.
Hit Count
82
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 10Medium-risk: admin panels, config files+60
Σ = 60
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-08-21 05:19:48
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 10 (+60)
2026-08-23 02:02:18
Last malicious request observed
Total score reached: 60/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

tzulo, inc.
AS11878 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

⚙️ Defensive Recommendations

Block 198.44.129.3 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

198.44.129.3 has been assigned a threat score of 60/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

📊 Threat Analysis

Network traffic from 198.44.129.3, located in Los Angeles, United States, operating on the network of tzulo, inc., has been classified as malicious by our automated threat scoring engine. Our sensors captured 82 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~82 requests per day. 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. Our records show 109 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. The score of 60/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

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)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS11878

68.235.46.24 (250)68.235.46.132 (230)23.234.100.38 (210)107.152.37.242 (165)23.234.72.38 (120)View all →
12

Security Intelligence

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

💡 Brute Force Attack Mechanics

Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.

🔍 Check Any IP Address

Share this report: