A recent supply-chain attack campaign compromised major technology companies including X (formerly Twitter), Vercel, Cursor, and Discord, impacting hundreds of organizations. The attack leveraged vulnerabilities in third-party dependencies or services to execute remote code execution (RCE), enabling attackers to infiltrate multiple targets. Although no known exploits are currently active in the wild, the campaign highlights the risks inherent in software supply chains. The attack requires no direct user interaction but exploits trust relationships between software providers and consumers. The medium severity rating reflects the significant confidentiality and integrity risks, balanced by the complexity of exploitation and limited current exploitation evidence. European organizations relying on affected platforms or similar supply-chain dependencies are at risk, especially in countries with high technology sector presence. Mitigation requires rigorous supply-chain security practices, including dependency auditing, strict access controls, and enhanced monitoring for anomalous activity. Countries like Germany, France, the UK, and the Netherlands are particularly vulnerable due to their large tech ecosystems and reliance on cloud services. Defenders should prioritize supply-chain risk management and incident response readiness to mitigate potential impacts from this evolving threat.
Hi all, I discovered suspicious behavior and possible malware in a file related to the official MicroDicom Viewer installer. I’ve documented everything including hashes, scan results, and my analysis in this public GitHub repository:
[https://github.com/darnas11/MicroDicom-Incident-Report](https://github.com/darnas11/MicroDicom-Incident-Report)
Feedback and insights are very welcome!
