
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: Go-http-client | Known bot/crawler User-Agent detected | +40 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Address UA spoofing from 136.144.43.149: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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.
136.144.43.149 has been assigned a threat score of 145/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
Threat intelligence analysis has linked 136.144.43.149 to malicious activity originating from Dallas, United States, operating on the network of Latitude.sh. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. United States currently accounts for 234 blocked IPs in our database, making it a significant source of malicious traffic. At 145/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.
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.
Containerized applications face unique security challenges including vulnerable base images, excessive privileges, shared kernel attacks, and insecure orchestration configurations. Runtime security monitoring and immutable container policies mitigate these risks.