
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Block scanning from 38.154.90.132: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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 |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 1344 | Unknown | Low | Service on port 1344 |
| 3128 | Unknown | Low | Service on port 3128 |
| 8000 | Unknown | Low | Service on port 8000 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8800 | Unknown | Low | Service on port 8800 |
| 21242 | Unknown | Low | Service on port 21242 |
| CVE ID | Link |
|---|---|
| CVE-2021-28652 | NVD → |
| CVE-2019-12528 | NVD → |
| CVE-2019-12523 | NVD → |
| CVE-2019-18679 | NVD → |
| CVE-2019-12521 | NVD → |
| CVE-2020-8449 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2020-8450 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2019-18678 | NVD → |
| CVE-2016-10002 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2016-10003 | NVD → |
| CVE-2018-19131 | NVD → |
| CVE-2020-24606 | NVD → |
| CVE-2020-11945 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2019-18676 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2023-49288 | NVD → |
🔴 This host has 57 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
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.
38.154.90.132 has been assigned a threat score of 105/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
38.154.90.132 is registered in Buffalo, United States, operating on the network of B2 Net Solutions Inc.. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 10 malicious requests from this address across a 19-day span, reflecting a sustained attack cadence of ~0.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. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 180 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 105/100, this is an extremely high-risk address. All traffic should be considered hostile.
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.
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.
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.