47.128.122.105📋 Copy

IP Intelligence Briefing: 47.128.122.105

Date: 2026-06-12

---

**1. Core Profile**

• Reputation: Moderate Risk (Risk Score: 40)
• Ownership:

- ASN: 16509

- Organization: Amazon Data Services Singapore (AMAZON-SIN)

- Geolocation: Singapore (City: Singapore, Latitude: 1.35, Longitude: 103.82)

• Network Role:

- Provider: Amazon Web Services (AWS)

- Type: CloudCompute (Firewalled / No Services)

- Subnet: 47.128.0.0/14

---

**2. Threat & Abuse Indicators**

• Threat Status: No direct malicious indicators (no malware, spam, or known attacker associations).
• Subnet Risk:

- Abuse Density: 55.26% (high abuse classification)

- Neighbor Analysis:

- Total Siblings: 38 IPs in 47.128.122.0/24

- Active Threat Siblings: 21 IPs (risk scores range: 0–50)

- Notable Neighbors:

- 47.128.122.100 (Risk: 40), 47.128.122.118 (Risk: 40), 47.128.122.122 (Risk: 50)

---

**3. Historical Observations**

• Geolocation Consistency: Inferred as Singapore with 56% confidence; ICMP validation blocked.
• Network Stability:

- Route Stability: Unstable (route changes detected in 30 days).

- DNSSEC: Validated.

• Threat Trends: No persistent malicious activity detected.

---

**4. Relationships & Dependencies**

• DNS Associations:

- Linked to AWS EC2 hostname: `ec2-47-128-122-105.ap-southeast-1.compute.amazonaws.com`.

• Network Relationships:

- Same network as AMAZON-SIN (AWS infrastructure).

• Control Plane:

- BGP Prefix: 47.128.0.0/14

- RPKI State: Not reported.

- Operator Score: 0.26 (Basic risk rating).

---

**5. Actionable Insights**

• Risk Mitigation:

- Monitor subnet for unusual traffic patterns due to high abuse density.

- Validate if the AWS instance is authorized (check access logs).

• Neighbor Analysis:

- Investigate high-risk neighbors (e.g., 47.128.122.122) for potential lateral movement or spoofing.

• Network Controls:

- Consider restricting traffic to/from this subnet if it contains untrusted hosts.

- Ensure AWS security groups and firewall rules are properly configured.

---

Conclusion:

The IP is a legitimate AWS cloud instance, but its subnet exhibits elevated risk due to neighboring IPs. SOC teams should prioritize monitoring the subnet and validating the necessity of the AWS resource. No immediate action is required for the IP itself, but proactive subnet-level analysis is recommended.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.