Adversaries may create or modify systemd services to repeatedly execute malicious payloads as part of persistence.
Skills in this repository
CyberStrikeus/CyberStrike - Page 92
SkillsMP has collected 7,442 skills from CyberStrikeus/CyberStrike. Open a skill to review its source and details.
CyberStrikeus/CyberStrikeShowing 40 of 7,442 collected skills.
Adversaries may create or modify Windows services to repeatedly execute malicious payloads as part of persistence.
Adversaries may create or modify Launch Daemons to execute malicious payloads as part of persistence.
Adversaries may create or modify container or container cluster management tools that run as daemons, agents, or services on individual hosts.
Adversaries may create or modify system-level processes to repeatedly execute malicious payloads as part of persistence.
Adversaries may maintain persistence through executing malicious content triggered using udev rules.
Adversaries may achieve persistence by leveraging Python’s startup mechanisms, including path configuration (`.pth`) files and the `sitecustomize.py` or `usercustomize.py` modules.
Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key.
Adversaries may abuse authentication packages to execute DLLs when the system boots.
Adversaries may abuse time providers to execute DLLs when the system boots.
Adversaries may abuse features of Winlogon to execute DLLs and/or executables when a user logs in.
Adversaries may abuse security support providers (SSPs) to execute DLLs when the system boots.
Adversaries may modify the kernel to automatically execute programs on system boot.
Adversaries may modify plist files to automatically run an application when a user logs in.
Adversaries may modify or add LSASS drivers to obtain persistence on compromised systems.
Adversaries may create or modify shortcuts that can execute a program during system boot or user login.
Adversaries may use port monitors to run an adversary supplied DLL during system boot for persistence or privilege escalation.
Adversaries may abuse print processors to run malicious DLLs during system boot for persistence and/or privilege escalation.
Adversaries may add or modify XDG Autostart Entries to execute malicious programs or commands when a user’s desktop environment is loaded at login.
Adversaries may achieve persistence by adding a Registry key to the Active Setup of the local machine.
Adversaries may add login items to execute upon user login to gain persistence or escalate privileges.
Adversaries may configure system settings to automatically execute a program during system boot or logon to maintain persistence or gain higher-level privileges on compromised systems.
Adversaries may modify host software binaries to establish persistent access to systems.
Adversaries may abuse dynamic-link library files (DLLs) in order to achieve persistence, escalate privileges, and evade defenses.
Adversaries may execute their own payloads by placing a malicious dynamic library (dylib) with an expected name in a path a victim application searches at runtime.
Adversaries may execute their own malicious payloads by hijacking the binaries used by an installer.
Adversaries may execute their own malicious payloads by hijacking environment variables the dynamic linker uses to load shared libraries.
Adversaries may execute their own malicious payloads by hijacking environment variables used to load libraries.
Adversaries may execute their own malicious payloads by hijacking the search order used to load other programs.
Adversaries may execute their own malicious payloads by hijacking vulnerable file path references.
Adversaries may execute their own malicious payloads by hijacking the binaries used by services.
Adversaries may execute their own malicious payloads by hijacking the Registry entries used by services.
Adversaries may leverage the COR_PROFILER environment variable to hijack the execution flow of programs that load the .NET CLR.
Adversaries may abuse the <code>KernelCallbackTable</code> of a process to hijack its execution flow in order to run their own payloads.
Adversaries may execute their own malicious payloads by hijacking how the .NET `AppDomainManager` loads assemblies.
Adversaries may execute their own malicious payloads by hijacking the way operating systems run programs.
Adversaries may impair a system's ability to hibernate, reboot, or shut down in order to extend access to infected machines.
Adversaries who successfully compromise a system may attempt to maintain persistence by “closing the door” behind them – in other words, by preventing other threat actors from initially accessing o...
Adversaries may achieve persistence by leveraging OAuth application integrations in a software-as-a-service environment.
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.