The malicious npm package js-logger-pack demonstrates how modern supply-chain attacks can hide in plain sight while leveraging trusted ecosystems. On the surface, the package behaves like a normal logging library, with its primary JavaScript file appearing harmless during casual inspection. The real attack begins during installation, where a concealed postinstall script executes automatically. This script runs a secondary file that quietly downloads a binary payload named MicrosoftSystem64 from an external repository. The process is designed to avoid suspicion by completing the installation normally while the malicious activity continues in the background. By packaging the payload as a cross-platform Node.js executable, the attackers ensure it works seamlessly across Windows, macOS, and Linux systems. Once the payload is active, it establishes persistence using platform-specific mechanisms, ensuring it remains active even after system restarts. It then connects to a remote control server to receive instructions and begin surveillance. The malware is capable of logging keystrokes, monitoring clipboard activity, and scanning files for sensitive data such as credentials or cryptocurrency wallets. It also enables attackers to execute commands remotely, manipulate files, and deploy additional malicious components. Because it operates without strict limitations, it can access a wide range of user data, making it particularly dangerous in development environments where secrets and tokens are often stored in plain text or configuration files. A notable aspect of this attack is the creative misuse of a legitimate AI hosting platform as both a distribution and exfiltration channel. Instead of relying solely on traditional servers, the malware uploads stolen data to private datasets controlled by the attacker, blending malicious traffic with normal usage patterns. It can also update itself by fetching new versions without verifying their authenticity, increasing its persistence and adaptability. Systems affected by this package should be treated as fully compromised, requiring immediate remediation steps such as rotating credentials, removing persistence mechanisms, cleaning dependencies, and reinstalling software securely.
CTM360 has uncovered a large-scale phishing campaign targeting the global insurance industry through sophisticated brand impersonation and AI-assisted social engineering techniques...
Researchers H0j3n and Aniq Fakhrul disclosed a proof-of-concept exploit named Certighost for CVE-2026-54121, an Active Directory Certificate Services (AD CS) vulnerability patched ...
At the core of an advanced malvertising attack scheme known as FakeAgent, SectopRAT was utilized by the cybercriminals in exploiting Anthropic’s Claude platform for the distribut...