IP Threat Report
120.28.109.104
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| POST requests present | Behavioral anomaly detected by automated analysis | +8 |
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 120.28.109.104 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
⚙️ General Security
Add 120.28.109.104 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 7547 | Unknown | Low | Service on port 7547 |
| CVE ID | Link |
|---|---|
| CVE-2007-3304 | NVD → |
| CVE-2003-0132 | NVD → |
| CVE-2011-3368 | NVD → |
| CVE-2003-0017 | NVD → |
| CVE-2021-44790 | NVD → |
| CVE-2004-1834 | NVD → |
| CVE-2022-37436 | NVD → |
| CVE-2011-3192 | NVD → |
| CVE-2004-0786 | NVD → |
| CVE-2003-1307 | NVD → |
| CVE-2010-1452 | NVD → |
| CVE-2007-6388 | NVD → |
| CVE-2021-32792 | NVD → |
| CVE-2017-9788 | NVD → |
| CVE-2002-1593 | NVD → |
| CVE-2012-0031 | NVD → |
| CVE-2011-2688 | NVD → |
| CVE-2025-49812 | NVD → |
| CVE-2011-4317 | NVD → |
| CVE-2022-28614 | NVD → |
| CVE-2022-28615 | NVD → |
| CVE-2012-4360 | NVD → |
| CVE-2005-2970 | NVD → |
| CVE-2007-5000 | NVD → |
| CVE-2003-0020 | NVD → |
🔴 Security scanning identified 114 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
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
120.28.109.104 has been assigned a threat score of 103/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
📊 Threat Analysis
Our monitoring infrastructure has identified 120.28.109.104, geolocated to San Juan, Philippines, operating on the network of Globe Telecom, as a source of suspicious network activity. During its 3-day observation window, we recorded 2 hostile requests from this IP — roughly 0.7 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Our records show 166 malicious IPs originating from Philippines, positioning it as a significant contributor to global threat activity. With a threat score of 103/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.
Related Threats
🇵🇭 Top threats from Philippines
194.61.41.46 (255)103.250.62.24 (213)180.191.168.156 (208)136.158.57.53 (208)136.158.82.180 (208)View all →Security Intelligence
💡 Server-Side Request Forgery (SSRF)
SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.
💡 TLS Fingerprinting (JA3/JA4)
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.