
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 65 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 15 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 51 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 184 | Medium-risk: admin panels, config files | +60 | |
| Burst: 53 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 21 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 54 | Medium-risk: admin panels, config files | +60 | |
| Burst: 56 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 81 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 48 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 109 | Medium-risk: admin panels, config files | +60 | |
| Burst: 48 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 130 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 64 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 164 | Medium-risk: admin panels, config files | +60 | |
| Burst: 49 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 151 req / 10s | Abnormally fast request rate — automated scanning | +35 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 74.248.144.152 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
IP 74.248.144.152 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 74.248.144.152.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 5432 | PostgreSQL | High | PostgreSQL database — direct database access risk |
⚠️ 1 high-risk port detected on 74.248.144.152. These services should not be publicly accessible without strict firewall rules.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
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.
74.248.144.152 has been assigned a threat score of 265/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
Network traffic from 74.248.144.152, located in Warsaw, Poland, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 5 malicious requests, averaging approximately 5 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Poland currently accounts for 102 blocked IPs in our database, making it a significant source of malicious traffic. A score of 265/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
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.
Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.