IP Threat Report
201.1.115.42
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| POST requests present | Behavioral anomaly detected by automated analysis | +8 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 201.1.115.42 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
🔎 Path Enumeration Protection
Block scanning from 201.1.115.42: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 6000 | Unknown | Low | Service on port 6000 |
| 6001 | Unknown | Low | Service on port 6001 |
| 6003 | Unknown | Low | Service on port 6003 |
| 6004 | Unknown | Low | Service on port 6004 |
| 6007 | Unknown | Low | Service on port 6007 |
| 6008 | Unknown | Low | Service on port 6008 |
| 6011 | Unknown | Low | Service on port 6011 |
| 6022 | Unknown | Low | Service on port 6022 |
| 6036 | Unknown | Low | Service on port 6036 |
| 6050 | Unknown | Low | Service on port 6050 |
| 6061 | Unknown | Low | Service on port 6061 |
| 6070 | Unknown | Low | Service on port 6070 |
| 8083 | Unknown | Low | Service on port 8083 |
| 8089 | Unknown | Low | Service on port 8089 |
| 8090 | Unknown | Low | Service on port 8090 |
| 8291 | MikroTik | High | MikroTik Winbox — router management, targeted by VPNFilter malware |
| 10050 | Unknown | Low | Service on port 10050 |
| 61617 | Unknown | Low | Service on port 61617 |
⚠️ Network scanning reveals 1 dangerous service exposed on 201.1.115.42. These services should not be publicly accessible without strict firewall rules.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
Blacklist Status (DNSBL)
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.
Threat Analysis
201.1.115.42 has been assigned a threat score of 103/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
Network traffic from 201.1.115.42, located in Botucatu, Brazil, operating on the network of Vivo, has been classified as malicious by our automated threat scoring engine. Our sensors captured 3 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~1 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 151 malicious IPs originating from Brazil, positioning it as a significant contributor to global threat activity. At 103/100, this is an extremely high-risk address. All traffic should be considered hostile.
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.
Related Threats
Security Intelligence
💡 Prototype Pollution 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.
💡 GDPR and Threat Intelligence
Processing IP addresses for security purposes under GDPR requires balancing legitimate interest in network protection with data minimization principles. Threat intelligence platforms must implement appropriate retention policies and provide mechanisms for data subject rights.