<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments for First Hackers News	</title>
	<atom:link href="https://firsthackersnews.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>https://firsthackersnews.com</link>
	<description>Latest cybersecurity news, real attacks, and practical IOCs—made simple and actionable.</description>
	<lastBuildDate>Tue, 16 Jun 2026 11:27:22 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		Comment on DeepSeek Repositories Scam Spreads Malware by Kling AI Motion Control		</title>
		<link>https://firsthackersnews.com/fake-deepseek-malware-github/#comment-27629</link>

		<dc:creator><![CDATA[Kling AI Motion Control]]></dc:creator>
		<pubDate>Tue, 16 Jun 2026 11:27:22 +0000</pubDate>
		<guid isPermaLink="false">https://firsthackersnews.com/?p=11690#comment-27629</guid>

					<description><![CDATA[The IoC breakdown here is genuinely useful, especially the persistence chain via scheduled tasks and SSH keys — that pattern is easy to overlook in fast triage. Beyond hash matching, treating every cloned repo as untrusted until release artifacts are validated against vendor-published checksums or signed manifests remains the strongest baseline. Worth pushing that habit upstream too: typo-squatted handles and impersonator repos in monitoring feeds are usually caught earlier than post-download sandboxing ever will.]]></description>
			<content:encoded><![CDATA[<p>The IoC breakdown here is genuinely useful, especially the persistence chain via scheduled tasks and SSH keys — that pattern is easy to overlook in fast triage. Beyond hash matching, treating every cloned repo as untrusted until release artifacts are validated against vendor-published checksums or signed manifests remains the strongest baseline. Worth pushing that habit upstream too: typo-squatted handles and impersonator repos in monitoring feeds are usually caught earlier than post-download sandboxing ever will.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on DeepSeek Repositories Scam Spreads Malware by video upscaler free		</title>
		<link>https://firsthackersnews.com/fake-deepseek-malware-github/#comment-27601</link>

		<dc:creator><![CDATA[video upscaler free]]></dc:creator>
		<pubDate>Mon, 15 Jun 2026 01:21:12 +0000</pubDate>
		<guid isPermaLink="false">https://firsthackersnews.com/?p=11690#comment-27601</guid>

					<description><![CDATA[The IoC breakdown here is genuinely useful, especially the persistence techniques tied to scheduled tasks and SSH keys — that pattern is easy to miss in a quick triage. Beyond hash matching, treating every cloned repo as untrusted until you have validated the release artifacts against the vendor published checksums or signatures remains the most reliable baseline. It is worth pushing that habit upstream too: alerting on typo-squatted repos and impersonator handles in monitoring feeds catches these campaigns earlier than post-download sandboxing ever will.]]></description>
			<content:encoded><![CDATA[<p>The IoC breakdown here is genuinely useful, especially the persistence techniques tied to scheduled tasks and SSH keys — that pattern is easy to miss in a quick triage. Beyond hash matching, treating every cloned repo as untrusted until you have validated the release artifacts against the vendor published checksums or signatures remains the most reliable baseline. It is worth pushing that habit upstream too: alerting on typo-squatted repos and impersonator handles in monitoring feeds catches these campaigns earlier than post-download sandboxing ever will.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on DeepSeek Repositories Scam Spreads Malware by MOV to MP3		</title>
		<link>https://firsthackersnews.com/fake-deepseek-malware-github/#comment-27594</link>

		<dc:creator><![CDATA[MOV to MP3]]></dc:creator>
		<pubDate>Sun, 14 Jun 2026 08:05:33 +0000</pubDate>
		<guid isPermaLink="false">https://firsthackersnews.com/?p=11690#comment-27594</guid>

					<description><![CDATA[Solid breakdown of the DeepSeek TUI impersonation campaign. The IoC list and persistence notes are particularly useful, and it underscores how easily an attacker can ride on the hype around a trending model. For anyone pulling binaries from GitHub, the lesson is straightforward: verify the publisher, cross-check the SHA-256 against an official release, and treat unverified installers as untrusted, regardless of how plausible the README looks.]]></description>
			<content:encoded><![CDATA[<p>Solid breakdown of the DeepSeek TUI impersonation campaign. The IoC list and persistence notes are particularly useful, and it underscores how easily an attacker can ride on the hype around a trending model. For anyone pulling binaries from GitHub, the lesson is straightforward: verify the publisher, cross-check the SHA-256 against an official release, and treat unverified installers as untrusted, regardless of how plausible the README looks.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on DeepSeek Repositories Scam Spreads Malware by image editor ai		</title>
		<link>https://firsthackersnews.com/fake-deepseek-malware-github/#comment-27581</link>

		<dc:creator><![CDATA[image editor ai]]></dc:creator>
		<pubDate>Sat, 13 Jun 2026 00:58:43 +0000</pubDate>
		<guid isPermaLink="false">https://firsthackersnews.com/?p=11690#comment-27581</guid>

					<description><![CDATA[Verifying a download&#039;s authenticity is becoming a real chore for users, especially when the project is being actively impersonated. In the OpenClaw case, taking a minute to check the publish date, commit history, and the presence of a signed release can save a lot of pain. Pairing that with a checksum comparison against the official site and, when available, PGP signature verification, makes the whole process far more reliable. Hashing the binary in question and matching it against the documented IoCs in this post is a practical first step before running anything.]]></description>
			<content:encoded><![CDATA[<p>Verifying a download&#8217;s authenticity is becoming a real chore for users, especially when the project is being actively impersonated. In the OpenClaw case, taking a minute to check the publish date, commit history, and the presence of a signed release can save a lot of pain. Pairing that with a checksum comparison against the official site and, when available, PGP signature verification, makes the whole process far more reliable. Hashing the binary in question and matching it against the documented IoCs in this post is a practical first step before running anything.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on DeepSeek Repositories Scam Spreads Malware by Photo to Video AI		</title>
		<link>https://firsthackersnews.com/fake-deepseek-malware-github/#comment-27569</link>

		<dc:creator><![CDATA[Photo to Video AI]]></dc:creator>
		<pubDate>Fri, 12 Jun 2026 02:12:47 +0000</pubDate>
		<guid isPermaLink="false">https://firsthackersnews.com/?p=11690#comment-27569</guid>

					<description><![CDATA[The OpenClaw link is the most telling part of this writeup - it shows the same operator keeps rotating across whichever AI name is trending, from DeepSeek to Claude, Grok, and FraudGPT. That kind of rebranding at scale only works because users skip basic verification steps like checking commit history, repo ownership, and checksums before downloading. These campaigns should be a reminder for anyone running local AI tooling, whether it is a CLI agent, an image-to-video workflow, or a model installer from GitHub Releases.]]></description>
			<content:encoded><![CDATA[<p>The OpenClaw link is the most telling part of this writeup &#8211; it shows the same operator keeps rotating across whichever AI name is trending, from DeepSeek to Claude, Grok, and FraudGPT. That kind of rebranding at scale only works because users skip basic verification steps like checking commit history, repo ownership, and checksums before downloading. These campaigns should be a reminder for anyone running local AI tooling, whether it is a CLI agent, an image-to-video workflow, or a model installer from GitHub Releases.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on DeepSeek Repositories Scam Spreads Malware by aiimagechecker		</title>
		<link>https://firsthackersnews.com/fake-deepseek-malware-github/#comment-27413</link>

		<dc:creator><![CDATA[aiimagechecker]]></dc:creator>
		<pubDate>Fri, 29 May 2026 18:59:26 +0000</pubDate>
		<guid isPermaLink="false">https://firsthackersnews.com/?p=11690#comment-27413</guid>

					<description><![CDATA[This is a critical reminder that popularity alone isn&#039;t enough to verify a repository&#039;s safety, especially for developer tools like DeepSeek TUI. The fact that attackers are hiding malicious payloads in standard 7z archives on the Releases page shows how sophisticated these social engineering tactics have become. Developers really need to double-check repository owners and validate all downloads with checksums before running anything locally.]]></description>
			<content:encoded><![CDATA[<p>This is a critical reminder that popularity alone isn&#8217;t enough to verify a repository&#8217;s safety, especially for developer tools like DeepSeek TUI. The fact that attackers are hiding malicious payloads in standard 7z archives on the Releases page shows how sophisticated these social engineering tactics have become. Developers really need to double-check repository owners and validate all downloads with checksums before running anything locally.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on DeepSeek Repositories Scam Spreads Malware by gptimg2img		</title>
		<link>https://firsthackersnews.com/fake-deepseek-malware-github/#comment-27050</link>

		<dc:creator><![CDATA[gptimg2img]]></dc:creator>
		<pubDate>Tue, 12 May 2026 17:06:53 +0000</pubDate>
		<guid isPermaLink="false">https://firsthackersnews.com/?p=11690#comment-27050</guid>

					<description><![CDATA[This is a critical reminder of how easily bad actors hide malware in standard archives like 7z on fake GitHub repos targeting tools like DeepSeek TUI. It really highlights why developers need to verify repository authenticity and signatures before downloading, rather than assuming the interface looks legitimate. Adding these specific IOCs to our internal blocklists immediately would be a crucial next step to protect teams from these deceptive updates.]]></description>
			<content:encoded><![CDATA[<p>This is a critical reminder of how easily bad actors hide malware in standard archives like 7z on fake GitHub repos targeting tools like DeepSeek TUI. It really highlights why developers need to verify repository authenticity and signatures before downloading, rather than assuming the interface looks legitimate. Adding these specific IOCs to our internal blocklists immediately would be a crucial next step to protect teams from these deceptive updates.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on UL — Global Safety Certification Giant Hit By Ransomware Attack by ParaSwap token PSP		</title>
		<link>https://firsthackersnews.com/ul-global-safety-certification-giant-hit-by-ransomware-attack/#comment-26155</link>

		<dc:creator><![CDATA[ParaSwap token PSP]]></dc:creator>
		<pubDate>Sat, 04 Apr 2026 21:42:35 +0000</pubDate>
		<guid isPermaLink="false">https://firsthackersnews.com/?p=3444#comment-26155</guid>

					<description><![CDATA[Cameron here — I’ve tried staking and the trustworthy service impressed me.]]></description>
			<content:encoded><![CDATA[<p>Cameron here — I’ve tried staking and the trustworthy service impressed me.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on A massive data breach on the Leak Zone Dark Web forum has resulted in the exposure of sensitive information, including the IP addresses and geographical locations of over 22 million users by Jordan Hamson		</title>
		<link>https://firsthackersnews.com/leakzone-data-breach-exposes-22-million-records/#comment-22253</link>

		<dc:creator><![CDATA[Jordan Hamson]]></dc:creator>
		<pubDate>Mon, 25 Aug 2025 12:42:48 +0000</pubDate>
		<guid isPermaLink="false">https://firsthackersnews.com/?p=10426#comment-22253</guid>

					<description><![CDATA[Some lady contacted me on IG and got me to trade with this company. Constantly convincing me for one reason to the other to keep increasing my deposits. Long story short, I lost about $88,000 I&#039;ve never been so disappointed in my life, trusted them only to be deceived like this. Just another one of those shady companies that have nothing to offer. Wish I had read some comments in forums earlier, wouldn&#039;t have dealt with them. Glad I found a reliable expert at Henry Walter in some forums who helped me get back everything I lost. If you&#039;re also a victim of these guys or lost your money to similar companies, write me and I&#039;ll refer you to the Recovery Experts. I&#039;ll make sure you get back everything you lost Email: davidmoore9951 (@) GM AIL , C0M]]></description>
			<content:encoded><![CDATA[<p>Some lady contacted me on IG and got me to trade with this company. Constantly convincing me for one reason to the other to keep increasing my deposits. Long story short, I lost about $88,000 I&#8217;ve never been so disappointed in my life, trusted them only to be deceived like this. Just another one of those shady companies that have nothing to offer. Wish I had read some comments in forums earlier, wouldn&#8217;t have dealt with them. Glad I found a reliable expert at Henry Walter in some forums who helped me get back everything I lost. If you&#8217;re also a victim of these guys or lost your money to similar companies, write me and I&#8217;ll refer you to the Recovery Experts. I&#8217;ll make sure you get back everything you lost Email: davidmoore9951 (@) GM AIL , C0M</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Why Indian Companies are not taking the Cyber Attack Seriously ? by Parker B		</title>
		<link>https://firsthackersnews.com/why-indian-companies-are-not-taking-the-cyber-attack-seriously/#comment-10725</link>

		<dc:creator><![CDATA[Parker B]]></dc:creator>
		<pubDate>Thu, 28 Apr 2022 03:15:31 +0000</pubDate>
		<guid isPermaLink="false">https://firsthackersnews.com/?p=4650#comment-10725</guid>

					<description><![CDATA[As mentioned, there are lack in cyber security awareness! Except for the keyword &quot;Hack&quot; 
:-D]]></description>
			<content:encoded><![CDATA[<p>As mentioned, there are lack in cyber security awareness! Except for the keyword &#8220;Hack&#8221;<br />
😀</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
