Ibrahim Saud
@tektrixIndiaCompletionist
2 followers18,458 downloads7,120 copies47 likes38,589 views
11,679 detections
Filters
Last updated
All Time
Detection languages
3,760
1,874
1,586
966
944
Categories
4,878
3,246
1,529
1,303
1,122
Platforms
7,678
1,824
1,066
999
986
Products / Services
2,963
1,768
1,278
953
798
MITRE Techniques
3,615
3,555
2,488
1,474
1,186
CVEs
36
27
26
25
23
IDS Classtypes
360
113
38
24
24
IDS Protocols
315
114
93
47
10
Detects instances where Node.js or NPM processes initiate common Windows discovery tools (e.g., systeminfo, whoami, tasklist, ipconfig, wmic). This behavior is often indicative of post-exploitation discovery or reconnaissance activity performed by an adversary utilizing an application or malicious script running within the Node.js runtime environment.
Detects the execution of Node.js lifecycle scripts (preinstall, postinstall, install-check, etc.) that trigger secondary process execution, such as command shells, downloaders (curl, wget), or security utilities (certutil, bitsadmin). This behavior is often associated with malicious npm package supply chain attacks aimed at downloading secondary payloads during installation.
Detects potential sideloading of malicious Chrome extensions by monitoring for unauthorized file creation of 'manifest.json' files within the browser's extension directories and unauthorized registry modifications related to extension management. The rule specifically excludes legitimate processes like 'chrome.exe' and 'GoogleUpdate.exe', aiming to identify third-party processes attempting to register or install browser extensions.
This rule monitors for file system operations (creation, modification, deletion, or renaming) performed by a Node.js process when interacting with sensitive directories and files associated with web browser extensions and cryptocurrency wallets. This pattern is commonly observed in credential and private key theft activities where malicious scripts attempt to exfiltrate wallet data.
Detects node.exe (often associated with malicious npm package runtimes) accessing local credential store files such as KeePass, 1Password, and Bitwarden. This activity is indicative of infostealer payloads (e.g., Miasma/MYRA) targeting developer workstations to exfiltrate sensitive credential databases.
This rule detects the creation or modification of Windows Registry Run keys that contain references to the Remcos remote access trojan path in 'ProgramData'. This pattern is commonly used by the Remcos RAT to achieve persistence upon user logon.
This rule detects when a Node.js process spawns common command-line interpreters (e.g., cmd.exe, powershell.exe, bash) with command-line arguments indicative of potentially malicious activity. This includes common software development script names, build-related tasks, or obfuscated command execution patterns. The rule excludes processes signed by trusted publishers like Microsoft or the OpenJS Foundation.
This rule detects when processes other than standard web browsers (Firefox, Chrome, Edge, IE) delete sensitive browser files such as 'cookies.sqlite', 'logins.json', 'Login Data', or 'Cookies'. This behavior is indicative of credential wiping or anti-forensics activity by malware, such as the Remcos RAT, attempting to clear evidence of browser activity.
This rule detects when a node.exe process, commonly used for executing npm lifecycle hooks (such as preinstall, postinstall, or various .cjs scripts), spawns suspicious child processes including shells (cmd.exe, powershell.exe, sh, bash) or scripting engines (wscript.exe, cscript.exe). This pattern is frequently observed in malicious npm packages designed to achieve code execution on a developer's machine during the package installation or build process.
This rule monitors for the Node.js process (node.exe or node) accessing common sensitive configuration files, SSH keys, cloud credentials, or environment files such as .ssh/id_rsa, .aws/credentials, .npmrc, and .docker/config.json. Such activity is often indicative of an adversary attempting to perform credential theft or environment discovery after gaining initial access via a compromised Node.js application.
Page 740 of 1168