Habr•October 28, 2026•🇷🇺Translated from Russian

Detecting Suspicious Processes in Linux: How to Investigate Unknown Services, Network Connections and Startup Tasks

Linux administrators often encounter situations where a server suddenly consumes more resources, unknown network connections appear, or a previously stopped process restarts after reboot. This does not always indicate a compromise and may result from faulty applications, incorrect service configurations, backup operations, or routine maintenance tasks.

Starting with Processes

Each running program instance receives a unique PID. To list processes sorted by CPU usage, run ps aux --sort=-%cpu | head -20. For memory consumption, use ps aux --sort=-%mem | head -20. Interactive monitoring is available via top or htop when installed.

High resource usage by an unexpected binary such as /opt/unknown/worker warrants further investigation. Useful details include the parent process ID, start time, and command line obtained with ps -p 1842 -o pid,ppid,user,lstart,etime,cmd.

Examining the Executable File

The actual binary path is revealed by readlink -f /proc/1842/exe. Command-line arguments are shown with ps -p 1842 -o args=. File metadata including owner and modification time can be checked using stat. On Debian-based systems, dpkg -S identifies the package owning a file when applicable.

Reviewing Network Connections

Listening TCP and UDP sockets are displayed with sudo ss -lntup, while established connections use sudo ss -tnp. The lsof -i command provides additional process-to-port mapping when available. LISTEN and ESTAB states indicate listening services and active connections respectively.

Checking systemd Services

Running services are listed via systemctl list-units --type=service --state=running. Unit files and failed services are examined with systemctl list-unit-files --type=service and systemctl --failed. Detailed status and configuration are retrieved using systemctl status and systemctl cat, paying special attention to the ExecStart directive.

Investigating Scheduled Tasks

User cron jobs are viewed with crontab -l. System-wide schedules reside in /etc/cron.d/, /etc/cron.hourly/, and similar directories. systemctl list-timers --all shows systemd timers. Each discovered job should be verified against system documentation and file ownership.

Auditing User Accounts and SSH Keys

Local users are enumerated with getent passwd. Accounts possessing UID 0 are identified by awk -F: '$3 == 0 {print $1 ":" $3}' /etc/passwd. Authorized SSH keys are typically stored in ~/.ssh/authorized_keys and should be compared against approved lists.

Correlating Events and Preserving Evidence

System logs are queried with sudo journalctl --since "today" or filtered by service name. When multiple indicators align, such as an unusual SSH login followed by new service creation and unexpected outbound connections, further investigation is warranted. If compromise is suspected, first record timestamps and preserve logs before remediation.

Related articles

AntiMalware•Other

Survey Shows 42% of Organizations Unify Multi-Vendor Security Tools into Single Protection Contour

A live AM Live broadcast on cybersecurity ecosystems revealed that 42% of participants have already combined solutions from multiple vendors into one unified security contour. Another 23% reported partial integration of tools, while 24% keep their protections operating independently and only 11% rely exclusively on a single vendor. Panelists emphasized the need for clear responsibility assignment, seamless data exchange, and formation of shared security context across products. Key selection criteria for ecosystems included breadth of product lines for 32% of viewers and discounts or bonuses for 28%. Experts advised practical testing of interoperability and evaluation of total cost of ownership before committing to any model. Service provider responsibilities for integration, SLA compliance, and outcomes must be defined in advance, according to CURATOR director Edgar Mikaelyan. After the session, 32% of attendees stated plans to launch or expand a security ecosystem project.

AntiMalware•Other

Yandex Tests Compass Device for Taxi Navigation During GPS Outages

Yandex is conducting trials of a compact Compass device in 10,000 taxis connected to its service to maintain accurate vehicle positioning when GPS signals are lost or jammed. The device connects to the OBD diagnostic port and pulls wheel speed data via the CAN bus while using its built-in gyroscope and accelerometer to determine direction of travel. These readings are sent over Bluetooth to the Yandex Pro driver app, which combines them with the last known GPS coordinates and frequent Wi-Fi access point scans to update the map in real time. The initiative addresses ongoing navigation problems that have affected Russian cities since spring 2022 and have been compounded by regular mobile internet outages since spring 2025. Earlier, Yandex tested a similar OBD-connected gadget called Yandex Pathfinder in 2023. The company has not disclosed timelines for completing the current trial or rolling the solution out more widely, though it plans to make Compass available to ordinary drivers later. Yandex navigation apps have also offered an offline step-by-step routing mode since 2025.

Habr•Other

Apple Attributes Widespread Service Outage to Faulty Internal IT Update

Apple has confirmed that the large-scale outage affecting its systems and user services on November 17, 2026, was caused by an incorrect internal update within the company's IT infrastructure. The incident impacted multiple consumer-facing services including the App Store, iCloud, Apple Pay, and Apple ID authentication. Users reported inability to download applications, sign in to accounts, or activate devices during the disruption. Internal corporate tools such as AppleWeb, AppleConnect, employee VPN access, corporate calendars, and the internal incident-tracking site were also taken offline. Retail operations in Apple Stores worldwide experienced interruptions to sales, repairs, and customer service processes. Company engineers restored most systems within four hours and stated they were working to return remaining services to normal operation as quickly as possible. Apple explicitly ruled out any external cyberattack or third-party interference as the cause of the outage.

Habr•Other

Global Outage Disrupts Apple Services Including App Store, iCloud and Apple Pay

On November 17, 2026, widespread disruptions affected multiple Apple services worldwide, including the App Store, iCloud, Apple Pay, and Apple ID authentication systems. The incident impacted users attempting to download applications on iPhone devices, sign into accounts, or activate new hardware. Apple confirmed problems with Apple Music and App Store functionality, along with performance degradation or complete unavailability of iCloud for all users. The outage was explicitly stated as unrelated to any country-level internet traffic filtering or restrictions. Service interruptions prevented normal operation of cloud storage, music streaming, and payment processing features tied to Apple ID. No official timeline for full restoration was provided in the initial reports from the company.