
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 26/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 44/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 48/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 54/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 80/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 84/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 31 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 47 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 54 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 55 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 84 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 66 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 | |
| UA changed for same IP | 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.
Block scanning from 207.241.173.115: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
IP 207.241.173.115 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Address UA spoofing from 207.241.173.115: 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.
207.241.173.115 has been assigned a threat score of 220/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:
The address 207.241.173.115 originates from Hauppauge, United States, operating on the network of Globecomm Network Services Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 13 days in our monitoring system, producing 598 flagged requests at a rate of ~46/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Our records show 150 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 220/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
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.
Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.