<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Securityresearch - Category - Forensic wheels</title><link>https://polymathmonkey.github.io/weblog/categories/securityresearch/index.html</link><description/><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 06 Jun 2026 13:27:31 +0200</lastBuildDate><atom:link href="https://polymathmonkey.github.io/weblog/categories/securityresearch/index.xml" rel="self" type="application/rss+xml"/><item><title>Tracking a credential scanner</title><link>https://polymathmonkey.github.io/weblog/securityresearch/hassh-redtail-cryptominer-campaign/index.html</link><pubDate>Sat, 06 Jun 2026 10:00:00 +0200</pubDate><guid>https://polymathmonkey.github.io/weblog/securityresearch/hassh-redtail-cryptominer-campaign/index.html</guid><description>The Alert At 10:23 on June 5th, ElastAlert fired a Pushover notification:
MISP Hit: Known Threat Actor IP: 130.12.180.51 | Canada Feed: Maltrail IOC for 2026-06-01 | Level: Medium What followed was a two-day investigation that started with a medium-severity feed match on a Canadian IP and ended with confirmed cryptominer deployment, SSH key persistence, and a second infrastructure node that the feed had never seen.</description></item></channel></rss>