
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| POST seen | Behavioral anomaly detected by automated analysis | +8 | |
| UA bot: python | Known bot/crawler User-Agent detected | +40 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
We have detected 31 malicious IPs from this autonomous system.
Address UA spoofing from 128.90.49.6: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
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.
128.90.49.6 has been assigned a threat score of 73/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
The following attack categories were identified:
Network traffic from 128.90.49.6, located in Singapore, Singapore, operating on the network of Powerhouse Management, Inc., has been classified as malicious by our automated threat scoring engine. Over a period of 2 days, this IP generated 69 malicious requests, averaging approximately 34.5 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. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. With 5,177 flagged addresses, Singapore represents a major presence in our threat database. A threat score of 73/100 places this IP in the high-risk category. Blocking at the firewall level is 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.
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.