New Developments in the Check Point Breach: CoreInjection’s Misleading Claims

Listen to this Post

Recent claims by the threat actor “CoreInjection” regarding the Check Point breach have been debunked. Hudson Rock’s analysis confirms that the leaked 350 user records originated from infostealer logs—unrelated to Check Point’s systems. This suggests CoreInjection is repackaging old data to exaggerate their involvement.

You Should Know: Investigating Infostealer Logs and Breach Attribution

1. Infostealer Logs Analysis

Infostealer malware (e.g., Lumma, Redline) harvests credentials from infected devices. These logs are often traded in cybercriminal forums. To check for infostealer infections on a Linux system:

grep -r "Lumma|Redline" /var/log/

Windows users can scan with:

Get-WinEvent -LogName Security | Where-Object { $_.Message -like "malware" }

2. Validating Breach Data

Use tools like `haveibeenpwned` or `DeHashed` to verify if leaked credentials are recycled from past breaches.

3. Detecting Credential Misuse

Monitor authentication logs for suspicious activity:

journalctl -u sshd --no-pager | grep "Failed password"

For Windows Event Logs:

Get-WinEvent -FilterHashtable @{LogName='Security'; ID=4625}

4. Underground Forum Monitoring

Threat actors often sell or repurpose breach data. Use OSINT tools like `SpiderFoot` or `Maltego` to track forum mentions.

5. Check Point’s Confirmed Scope

Check Point’s breach involved credential misuse. Reset all related passwords and enforce MFA:

 Linux: Force password change for all users 
chage -d 0 $(awk -F: '{print $1}' /etc/passwd)

What Undercode Say

CoreInjection’s false claims highlight the importance of verifying breach narratives. Always:
– Cross-reference leaks with historical data.
– Monitor for credential stuffing attacks.
– Isolate breach artifacts (e.g., screenshots) using tools like `exiftool` to check metadata:

exiftool -a suspicious_image.png

– Use `YARA` rules to detect infostealer payloads:

yara -r infostealer.yar /malware_samples/

Expected Output:

A clear distinction between actual breaches and opportunistic claims, backed by actionable commands for defenders.

Related URLs:

References:

Reported By: Alon Gal – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅

Join Our Cyber World:

💬 Whatsapp | 💬 TelegramFeatured Image