This IP address has been reported a total of
4
times from
2 distinct
sources.
182.1.132.124 was first reported on
, and the most recent report was
.
Recent Reports:
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
Suspicious activity detected from IP 182.1.132.124 based on mailserver logs.
Sample logs:
2026-07-31 ...
show moreSuspicious activity detected from IP 182.1.132.124 based on mailserver logs.
Sample logs:
2026-07-31 11:50:37,050 INFO [ImapServer-1657] [ip=172.16.0.182;oip=182.1.132.124;via=com.google.android.gm,172.16.0.182(nginx/1.24.0);ua=Zimbra/24.9.7_ZEXTRAS_202410;cid=1242;] imap - LOGIN elapsed=2 (NIO)
2026-07-31 11:50:48,194 INFO [ImapServer-1656] [ip=172.16.0.182;cid=1244;oip=182.1.132.124;via=com.google.android.gm,172.16.0.182(nginx/1.24.0);ua=Zimbra/24.9.7_ZEXTRAS_202410;] imap - ID elapsed=0 (NIO)
2026-07-31 11:50:48,198 INFO [ImapServer-1657] [ip=172.16.0.182;oip=182.1.132.124;via=com.google.android.gm,172.16.0.182(nginx/1.24.0);ua=Zimbra/24.9.7_ZEXTRAS_202410;cid=1244;] imap - authentication failed for [**] (LDAP error: - unable to ldap authenticate: invalid credentials)
2026-07-31 11:50:48,198 INFO [ImapServer-1657] [ip=172.16.0.182;oip=182.1.132.124;via=com.google.android.gm,172.16.0.182(nginx/1.24.0);ua=Zimbra/24.9.7_ZEXTRAS_202410;cid=1244;] account - Error occurred during aut
show less
Distributed application-layer DoS against git.mills.io (self-hosted Gitea). High-volume automated re ...
show moreDistributed application-layer DoS against git.mills.io (self-hosted Gitea). High-volume automated requests to expensive Git repository endpoints (commit/diff/blame/archive views), ~1 request per IP, spoofed browser UA, rejected with HTTP 429. Residential-proxy botnet campaign, 2026-06-13/14 UTC.
show less
Suspicious activity detected from IP 182.1.132.124 based on mailserver logs.
Sample logs:
2026-05-30 ...
show moreSuspicious activity detected from IP 182.1.132.124 based on mailserver logs.
Sample logs:
2026-05-30 05:24:59,874 INFO [ImapServer-5327] [ip=172.16.0.182;oip=182.1.132.124;via=com.google.android.gm,172.16.0.182(nginx/1.24.0);ua=Zimbra/24.9.7_ZEXTRAS_202410;cid=4899;] imap - LOGIN elapsed=1 (NIO)
2026-05-30 05:25:10,695 INFO [ImapServer-5327] [ip=172.16.0.182;cid=4900;oip=182.1.132.124;via=com.google.android.gm,172.16.0.182(nginx/1.24.0);ua=Zimbra/24.9.7_ZEXTRAS_202410;] imap - ID elapsed=0 (NIO)
2026-05-30 05:25:10,696 INFO [ImapServer-5327] [ip=172.16.0.182;oip=182.1.132.124;via=com.google.android.gm,172.16.0.182(nginx/1.24.0);ua=Zimbra/24.9.7_ZEXTRAS_202410;cid=4900;] imap - authentication failed for [**] (LDAP error: - unable to ldap authenticate: invalid credentials)
2026-05-30 05:25:10,696 INFO [ImapServer-5327] [ip=172.16.0.182;oip=182.1.132.124;via=com.google.android.gm,172.16.0.182(nginx/1.24.0);ua=Zimbra/24.9.7_ZEXTRAS_202410;cid=4900;] account - Error occurred during aut
show less
Suspicious activity detected from IP 182.1.132.124 based on mailserver logs.
Sample logs:
2026-04-10 ...
show moreSuspicious activity detected from IP 182.1.132.124 based on mailserver logs.
Sample logs:
2026-04-10 04:41:06,319 INFO [ImapServer-4105] [ip=172.16.0.182;oip=182.1.132.124;via=com.google.android.gm,172.16.0.182(nginx/1.24.0);ua=Zimbra/24.9.7_ZEXTRAS_202410;cid=10196;] imap - LOGIN elapsed=2 (NIO)
2026-04-10 04:41:16,853 INFO [ImapServer-4105] [ip=172.16.0.182;cid=10197;oip=182.1.132.124;via=com.google.android.gm,172.16.0.182(nginx/1.24.0);ua=Zimbra/24.9.7_ZEXTRAS_202410;] imap - ID elapsed=0 (NIO)
2026-04-10 04:41:16,854 INFO [ImapServer-4105] [ip=172.16.0.182;oip=182.1.132.124;via=com.google.android.gm,172.16.0.182(nginx/1.24.0);ua=Zimbra/24.9.7_ZEXTRAS_202410;cid=10197;] imap - authentication failed for [**] (LDAP error: - unable to ldap authenticate: invalid credentials)
2026-04-10 04:41:16,854 INFO [ImapServer-4105] [ip=172.16.0.182;oip=182.1.132.124;via=com.google.android.gm,172.16.0.182(nginx/1.24.0);ua=Zimbra/24.9.7_ZEXTRAS_202410;cid=10197;] account - Error occurred during
show less
Brute-Force
Showing 1 to
4
of 4 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown ๐ฉ