malware-analysis

[0x100001060]> pia 4
str z21, [x2, 0x4a, mul vl]
???
???
???
[0x100001060]> pia 8
str z21, [x2, 0x4a, mul vl]
???
???
???
invalid
???
???
???
[0x100001060]> p8 8
554889e541574156
[0x100001060]> e asm.arch;e asm.bits
arm
64
[0x100001060]>

Matched on: ::
Name: Internet Protocol (IP) Address Version 6
Link:  https://www.shodan.io/host/::

This shouldn't match.

Tl;dr: Use the workaround from https://github.com/pwndbg/pwndbg/pull/322/files only for broken gdb versions

Problem in MISP/app/Lib/Export/NidsExport.php /
causes there are two rows in beggening of all rules regarding email. Bug is in row 161

case 'email':
$this->emailSrcRule($ruleFormat, $item['Attribute'], $sid);
$this->emailDstRule($ruleFormat, $item['Attribute'], $sid);
break;
this causes inserting both source and destinati

Seeing PGO: UNKNOWN is not implemented yet! printed out when parsing the following assembly

global main
extern GetStdHandle
extern WriteFile

section .text
main:
    mov     rcx, 0fffffff5h
    call    GetStdHandle

    mov     rcx, rax
    mov     rdx, NtlpBuffer
    mov     r8, [NtnNBytesToWrite]
    mov     r9, NtlpNBytesWritten
    sub     rsp, 40
    mov     dword [rs

in some cases, f-strings can be easier for humans to read and result in fewer characters/lines. they are supported from py3.6 onwards, so they're now acceptable to use within capa.

we should use f-strings where they make sense. furthermore, we should define what "make sense" means.

notably, we should not use f-strings in calls to logging.

![image](https://user-images.githubusercontent