Malicious code in syjoy (npm)

The npm package syjoy (version 1.0.0) contains a malicious payload implemented in Python (pointer.py) that is installed and executed silently upon first use. The payload installs Python 3.12 if not present, runs with elevated privileges and hidden windows, and performs extensive data harvesting including global keyboard hooks, clipboard reading, screenshots, and UI Automation tree traversal to extract text from arbitrary windows. Harvested data is exfiltrated to a hardcoded endpoint (https://new-pointer.vercel.app/api). The remote server can send back commands that are injected as keyboard input into the host system, enabling remote control. The package's user interface is designed to be invisible and obfuscates window titles. Internal mode names suggest the tool is intended for covert assessments or cheating overlays rather than legitimate system configuration.

This malicious package compromises user privacy by harvesting sensitive data such as keystrokes, clipboard contents, screenshots, and application text. It also enables remote attackers to inject arbitrary keyboard input into the victim's system, potentially allowing unauthorized actions or manipulation of applications. The silent installation of Python and use of elevated privileges increase the risk of undetected persistence and control. This can lead to data leakage, unauthorized system control, and potential further compromise of the host environment.

No official patch or remediation is currently documented. Users should immediately uninstall the syjoy package version 1.0.0 and avoid installing it. Since the package installs Python silently and runs hidden scripts, affected systems should be scanned for the presence of the Python payload (pointer.py) and any related artifacts such as start_tool.vbs. Network monitoring for connections to https://new-pointer.vercel.app/api may help detect compromise. Consider restricting npm package sources to trusted repositories and auditing dependencies before installation. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for updates.