[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] IP 169.40.142.172 targeted api.majikah. ...
show more[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] IP 169.40.142.172 targeted api.majikah.solutions with repeated GET requests to /api/session/properties using a Metabase vulnerability scanner user-agent. This activity coincides with 898 external AbuseIPDB reports confirming high-volume malicious behavior. Likely motive: Vulnerability scanning
show less
[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] IP 130.12.180.164 generated 1 local hit ...
show more[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] IP 130.12.180.164 generated 1 local hit against the root endpoint GET / on api.majikah.solutions, triggering rate-limiting rules. External telemetry reports 234 total abuse incidents with the most recent report occurring minutes prior to local observation, confirming ongoing malicious activity. Likely motive: automated web scraping or scanning
show less
[AI Threat Score: 65/100 via Gemini] [AbuseIPDB Score: 19] IP address 154.28.229.79 generated 4 loca ...
show more[AI Threat Score: 65/100 via Gemini] [AbuseIPDB Score: 19] IP address 154.28.229.79 generated 4 local hits against majikah.solutions using browser impersonation headers and conducting path enumeration across endpoints including /support, /articles/ml-dsa-87-strongest-post-quantum-signature, /developer, and /sdk. CrowdSec corroborates this activity with a suspicious reputation and behaviors including http:scan, http:crawl, http:exploit, and http:dos, alongside 27 historical external reports on AbuseIPDB. Likely motive: Automated web application reconnaissance and probing
show less
[AI Threat Score: 45/100 via Gemini] [AbuseIPDB Score: 9] IP 104.250.211.7 executed a GET request to ...
show more[AI Threat Score: 45/100 via Gemini] [AbuseIPDB Score: 9] IP 104.250.211.7 executed a GET request to /developer on majikah.solutions using browser-impersonation headers, triggering malicious-request and repeated-reconnaissance rules. Although AbuseIPDB reports a low confidence score of 9 percent with 4 external reports, CrowdSec independently flags the IP as suspicious with high confidence and behaviors including http:crawl, http:dos, and http:scan. Likely motive: Automated web crawling and reconnaissance using browser impersonation.
show less
[AI Threat Score: 45/100 via Gemini] [AbuseIPDB Score: 35] IP 154.28.229.247 generated a single loca ...
show more[AI Threat Score: 45/100 via Gemini] [AbuseIPDB Score: 35] IP 154.28.229.247 generated a single local request to GET /products/majik-signature using a mobile browser user-agent string while exhibiting malicious-request and browser-impersonation patterns. Historical telemetry shows 19 external reports with the most recent occurrence on October 15, 2026, and an Abuse Confidence Score of 35%, confirming ongoing suspicious automated behavior. Likely motive: Automated web scraping and reconnaissance
show less
[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] The IP address 93.123.109.247 targeted ...
show more[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] The IP address 93.123.109.247 targeted the public API endpoint GET /healthz using the user-agent tlm-scanner/2.0, triggering local rate-limiting rules. This activity aligns with a massive global reputation profile consisting of 165 external reports, with the most recent report arriving on 2026-10-16T19:16:43.000Z. Likely motive: Automated reconnaissance and endpoint enumeration
show less
[AI Threat Score: 14/100 via Gemini] [AbuseIPDB Score: 14] IP 35.255.243.214 generated a single loca ...
show more[AI Threat Score: 14/100 via Gemini] [AbuseIPDB Score: 14] IP 35.255.243.214 generated a single local hit on 2026-10-16 via GET / using the CMS-Checker/1.0 user-agent, triggering rate-limiting rules. AbuseIPDB shows a low confidence score of 14 percent with two external reports, while CrowdSec reports an unknown reputation and no malicious behaviors. Likely motive: Automated content management system enumeration
show less
[AI Threat Score: 74/100 via Gemini] [AbuseIPDB Score: 74] IP 188.166.188.190 generated 4 local requ ...
show more[AI Threat Score: 74/100 via Gemini] [AbuseIPDB Score: 74] IP 188.166.188.190 generated 4 local requests targeting path patterns such as //blog/robots.txt, //blog/, //wordpress/, and //wp/, triggering rate-limits. This activity is supported by 12 external reports on AbuseIPDB with an abuse confidence score of 74%, indicating active web enumeration. Likely motive: Web application reconnaissance and directory enumeration
show less
[AI Threat Score: 72/100 via Groq] [AbuseIPDB Score: 95] The IP made two GET '/' requests to api.maj ...
show more[AI Threat Score: 72/100 via Groq] [AbuseIPDB Score: 95] The IP made two GET '/' requests to api.majikah.solutions within seconds, both triggering the rate‑limit rule. AbuseIPDB lists a 95% confidence score with 17 recent reports, the latest only minutes after the local activity, marking the address as a known malicious source. This behavior aligns with a generic high‑volume web bot, fitting the BAD WEB BOT category. Likely motive: Automated web bot issuing rapid requests to the target site
show less
[AI Threat Score: 68/100 via Groq] [AbuseIPDB Score: 28] The IP made 17 requests within minutes, rep ...
show more[AI Threat Score: 68/100 via Groq] [AbuseIPDB Score: 28] The IP made 17 requests within minutes, repeatedly probing for private keys (/id_rsa, /id_ed25519) and enumerating paths (/__vite_rsc_findSourceMapURL, /%2Fdashboard). High‑severity tags (critical, credential‑probe) and repeated‑reconnaissance indicate targeted web app scanning. CrowdSec flags http:scan and http:dos, corroborating the aggressive reconnaissance observed in the local logs. Likely motive: Credential harvesting and web‑application reconnaissance
show less
[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] The IP address 45.138.12.24 executed a ...
show more[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] The IP address 45.138.12.24 executed a targeted request to retrieve sensitive system process environment variables via the endpoint GET /proc/self/environ on majikah.solutions. This request triggered critical rule violations including process-file-probe and malicious-request. Furthermore, this activity is strongly corroborated by AbuseIPDB telemetry, which shows a 100% abuse confidence score and 2440 total external reports, with the most recent report occurring minutes after the local hit. Likely motive: System reconnaissance and unauthorized information disclosure
show less
[AI Threat Score: 65/100 via Gemini] [AbuseIPDB Score: 35] The IP address 34.75.64.113 generated 9 l ...
show more[AI Threat Score: 65/100 via Gemini] [AbuseIPDB Score: 35] The IP address 34.75.64.113 generated 9 local requests demonstrating malicious reconnaissance and credential probing. The activity includes targeted requests to sensitive system and environment files such as GET /proc/self/cmdline and GET /@fs/proc/self/environ, directory traversal attempts via GET /userfiles, a credential probe targeting GET /id_ed25519, and a POST request. CrowdSec corroborates this activity with a high confidence http:scan behavior, matching MITRE technique T1595. Likely motive: system reconnaissance and credential harvesting
show less
[AI Threat Score: 65/100 via Gemini] [AbuseIPDB Score: 14] This IP executed 2 malicious requests tar ...
show more[AI Threat Score: 65/100 via Gemini] [AbuseIPDB Score: 14] This IP executed 2 malicious requests targeting signature.majikah.solutions, specifically probing the sensitive local path /@fs/proc/self/environ and attempting a query traversal via /_image using a ChatGPT user-agent string. CrowdSec corroborates this activity by identifying a known malicious reputation with behaviors in http:scan and http:dos, while external AbuseIPDB reports confirm ongoing targeting. Likely motive: Information disclosure and web application vulnerability probing
show less
[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] The IP address 45.138.12.185 executed r ...
show more[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] The IP address 45.138.12.185 executed reconnaissance requests targeting sensitive endpoints, specifically requesting GET /secrets on majikah.solutions and developers.majikah.solutions, followed by GET / on api.majikah.solutions. This behavior triggered critical tags for credential probes and configuration secret exposure. External telemetry confirms heavy malicious activity with 425 total reports and a 100% Abuse Confidence Score. Likely motive: Credential harvesting and configuration data theft
show less
[AI Threat Score: 68/100 via Gemini] [AbuseIPDB Score: 68] The IP address 172.233.156.98 issued a si ...
show more[AI Threat Score: 68/100 via Gemini] [AbuseIPDB Score: 68] The IP address 172.233.156.98 issued a single request to the endpoint GET / on api.majikah.solutions, triggering a rate-limit rule. This localized event aligns with a broader history of malicious behavior reflected in 63 external AbuseIPDB reports, the most recent occurring on October 14, 2026, contributing to an Abuse Confidence Score of 68%. Likely motive: Automated web scraping or scanning.
show less
[AI Threat Score: 78/100 via Gemini] [AbuseIPDB Score: 78] The IP 172.236.112.76 generated a single ...
show more[AI Threat Score: 78/100 via Gemini] [AbuseIPDB Score: 78] The IP 172.236.112.76 generated a single local hit accessing GET / on api.majikah.solutions using a standard Chrome user-agent, triggering a rate-limit rule. Historical AbuseIPDB telemetry shows a high abuse confidence score of 78% with 108 total external reports, the most recent occurring approximately one hour prior to the local activity. Likely motive: Automated web scraping or crawling by a misconfigured or aggressive bot.
show less
[AI Threat Score: 73/100 via Gemini] [AbuseIPDB Score: 73] The IP 34.169.173.186 generated 2 local h ...
show more[AI Threat Score: 73/100 via Gemini] [AbuseIPDB Score: 73] The IP 34.169.173.186 generated 2 local hits targeting GET / on api.majikah.solutions with a rate-limit trigger. External AbuseIPDB telemetry shows 12 reports with an abuse confidence score of 73%, and the most recent report occurred on 2026-10-16T10:20:29.000Z. Likely motive: Automated scraping or probing via web bot
show less
[AI Threat Score: 65/100 via Gemini] [AbuseIPDB Score: 14] IP 34.207.140.43 executed repeated reconn ...
show more[AI Threat Score: 65/100 via Gemini] [AbuseIPDB Score: 14] IP 34.207.140.43 executed repeated reconnaissance requests against majikah.solutions, accessing GET / three times and GET /privacy once using browser impersonation headers. CrowdSec CTI confirms malicious behaviors including http:scan, http:exploit, and http:crawl associated with MITRE technique T1595. Combined with 15 external AbuseIPDB reports, this activity demonstrates automated web scanning and application probing. Likely motive: Automated web application scanning and reconnaissance
show less
[AI Threat Score: 25/100 via Gemini] [AbuseIPDB Score: 24] IP 104.236.201.119 generated 2 local hits ...
show more[AI Threat Score: 25/100 via Gemini] [AbuseIPDB Score: 24] IP 104.236.201.119 generated 2 local hits against api.majikah.solutions requesting GET / and GET /favicon.ico, triggering rate-limiting rules. Historical telemetry shows 3 external reports on AbuseIPDB with a confidence score of 24%, while CrowdSec flags the IP with an http:scan behavior. Likely motive: Automated web scanning
show less
[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] This IP targeted the endpoint GET /.git ...
show more[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] This IP targeted the endpoint GET /.git/config on api.majikah.solutions, triggering source-control and git-metadata detection rules. Historical AbuseIPDB telemetry confirms 65 total external reports with an abuse confidence score of 100%, and CrowdSec independently corroborates this malicious activity with a known reputation and HTTP scanning behavior. Likely motive: Source control enumeration
show less
[AI Threat Score: 83/100 via Gemini] [AbuseIPDB Score: 83] The IP address 2a01:4f8:c014:b22b::1 perf ...
show more[AI Threat Score: 83/100 via Gemini] [AbuseIPDB Score: 83] The IP address 2a01:4f8:c014:b22b::1 performed a GET request to the root endpoint / on api.majikah.solutions, triggering a rate-limit rule. Historical AbuseIPDB telemetry records 32 external reports with an abuse confidence score of 83%, confirming ongoing malicious behavior up to October 14, 2026. Likely motive: Automated web scraping or scraping abuse
show less
[AI Threat Score: 95/100 via Gemini] [AbuseIPDB Score: 100] The IP address 146.70.40.70 generated 2 ...
show more[AI Threat Score: 95/100 via Gemini] [AbuseIPDB Score: 100] The IP address 146.70.40.70 generated 2 local hits targeting GET / on api.majikah.solutions, triggering rate-limit rules. Historical telemetry shows 1,294 external reports with an Abuse Confidence Score of 100%, indicating widespread automated scanning. Likely motive: Automated web scraping and reconnaissance
show less
[AI Threat Score: 85/100 via Gemini] [AbuseIPDB Score: 100] The IP 66.132.195.97, associated with Ce ...
show more[AI Threat Score: 85/100 via Gemini] [AbuseIPDB Score: 100] The IP 66.132.195.97, associated with CensysInspect, generated 1 local hit requesting GET / on api.majikah.solutions using a known bot user-agent and triggering a rate-limit. Historical AbuseIPDB telemetry shows 2470 external reports with a 100% abuse confidence score, the most recent external report occurring just minutes after the local observation. Likely motive: Automated reconnaissance and scanning by an internet-wide survey bot.
show less
[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] The IP address 85.217.149.15 executed a ...
show more[AI Threat Score: 100/100 via Gemini] [AbuseIPDB Score: 100] The IP address 85.217.149.15 executed a request to the root endpoint of api.majikah.solutions using the custom User-Agent 'ModatScanner/1.2 (+https://modat.io/)', triggering a local rate-limit rule. This behavior aligns with massive historical abuse, evidenced by 2399 external reports on AbuseIPDB and an Abuse Confidence Score of 100%, with the most recent external report occurring just minutes prior. Likely motive: Automated web crawling and data scraping
show less
Bad Web BotWeb App Attack
By clicking “Accept all”, you agree to the storing of cookies on your device to remember preferences and
analyze site usage.
Read more
- Required to log into your AbuseIPDB account, and store these cookie preferences.