ABUSE.MOM
THREAT REPORT

IP Threat Report
151.244.0.40

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 06:30:44
First seen: 2026-04-16 18:27:06
Last seen: 2026-04-16 18:27:06
70

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 70/100. Total malicious requests observed: 1.

FORM_SPAM
01

Geolocation & Classification

IP Address
151.244.0.40
Type
Hosting
Country
🇯🇵 Japan
City
Tokyo
ISP
FDCservers.net
Organization
Unknown
Autonomous System
AS30058 FDCservers.net
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Form spam: no_js_checkSpam/malware keywords in request content+0
Σ = 0
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-04-16 18:27:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Form spam: no_js_check
2026-04-16 18:27:06
Last malicious request observed
Total score reached: 70/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

FDCservers.net
AS30058 · 🇯🇵 Japan
06

Recommendations

Actions taken & recommended

  • IP 151.244.0.40 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

📧 Content Abuse Prevention

IP 151.244.0.40 is flooding forms with spam. Implement time-based tokens and block IPs submitting more than 5 forms per hour.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

151.244.0.40 has been assigned a threat score of 70/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

📊 Threat Analysis

Network traffic from 151.244.0.40, located in Tokyo, Japan, operating on the network of FDCservers.net, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. 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. Our records show 102 malicious IPs originating from Japan, positioning it as a significant contributor to global threat activity. A threat score of 70/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.

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.

11

Related Threats

🇯🇵 Top threats from Japan

103.163.220.216 (340)35.243.110.60 (288)20.89.56.154 (280)20.27.221.169 (280)20.210.188.132 (280)View all →

🏢 Same network: AS30058

64.139.50.130 (105)50.7.230.162 (105)64.144.6.133 (90)67.159.24.34 (80)50.7.124.7 (70)View all →
12

Security Intelligence

💡 SQL Injection Campaigns

SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.

💡 WebSocket Security Considerations

WebSocket connections bypass traditional HTTP security controls, creating opportunities for cross-site WebSocket hijacking, denial of service, and data injection. Proper origin validation, authentication, and message rate limiting are essential for secure WebSocket implementations.

🔍 Check Any IP Address

Share this report: