Quantcast
Channel: hashcat Forum - All Forums
Viewing all 8224 articles
Browse latest View live
↧

the speed drops after some time

January 2, 2025, 3:02 am
$
0
0
Maybe it should be like that, but I'll ask the experts.

When the dictionary attack starts, the speed is excellent, but after some time, I see that the speed drops by about 6 times, if it was 1.2 million per second, then the output will be about 240 thousand.

maybe some additional options need to be written in the command or the dictionaries need to be optimized somehow, what do you advise.

and yes, my dictionaries are from 10 GB and above, some are 80 GB
↧
Search

Found winrar password but wrong

January 3, 2025, 10:46 am
$
0
0
So, I have a compressed archive of WinRAR (128 bit AES, SHA1) with a hash like $RAR3$*1*here_is_long_hash:33. I extracted it with rar2john. 

I launched the hashcat, algorithm 23800 and in just a few years of searching I found a password for this hash!
Hashcat put it in the file RAR3$*1*here_is_long_hash:33:found_password. And this password successfully opened the archive. 

But there is some oddity. The file in the archive is 192 kilobytes (and compressed to 40 kilobytes), but the extracted file is only 100 bytes. The archive test with this password is successful, opening is successful, but the file is damaged. Actually CRC32 is OK, size is not OK.

Is it possible that several passwords are suitable for the WinRAR archive? What should I do in this case, I would like to continue the search but I do not understand how I can use the extracted password
↧
↧

hiprtcCompileProgram is missing from HIPRTC shared library.

January 3, 2025, 4:01 pm
$
0
0
Code:
PS C:\Users\kenobi\Desktop\hashcat-6.2.6> .\hashcat.exe -b
hashcat (v6.2.6) starting in benchmark mode

Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

hiprtcCompileProgram is missing from HIPRTC shared library.

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

OpenCL API (OpenCL 2.1 AMD-APP (3628.0)) - Platform #1 [Advanced Micro Devices, Inc.]
=====================================================================================
* Device #1: AMD Radeon(TM) Graphics, 6144/12400 MB (5052 MB allocatable), 1MCU
* Device #2: AMD Radeon RX 7800 XT, 16256/16368 MB (13912 MB allocatable), 30MCU

I receive this warning when i attempt to run a benchmark. Im using a 7800xt with a Ryzen 7 9700x, with gpu drivers fully up to date on a fresh windows 11 install. I also tried installing the AMD HIP SDK, but it didn't do anything. Any ideas on how to get rid of this warning?
↧

Errors running hashcat with Surface Laptop 7 ARM64

January 4, 2025, 3:17 pm
$
0
0
Hi,

Having an issue with hashcat with my new Surface Laptop Pro. It has the SnapdragonX 12-core X1E80100, 64GB.

When running the binaries I get an error " Device #1: Kernel ./OpenCL/shared.cl build failed."

When I run hashcat -I this is the output I get.

PS C:\Hashcat\hashcat-6.2.6> .\hashcat.exe -I
hashcat (v6.2.6) starting in backend information mode

OpenCL Info:
============

OpenCL Platform ID #1
  Vendor..: QUALCOMM
  Name....: QUALCOMM Snapdragon(TM)
  Version.: OpenCL 3.0 QUALCOMM build: commit unknown

  Backend Device ID #1
    Type...........: GPU
    Vendor.ID......: 2147483648
    Vendor.........: QUALCOMM
    Name...........: Qualcomm(R) Adreno(TM) X1-85 GPU
    Version........: OpenCL 3.0 Qualcomm(R) Adreno(TM) X1-85 GPU
    Processor(s)...: 6
    Clock..........: 1
    Memory.Total...: 32508 MB (limited to 1024 MB allocatable in one block)
    Memory.Free....: 15808 MB
    Local.Memory...: 32 KB
    OpenCL.Version.: OpenCL C 3.0 Qualcomm(R) Adreno(TM) X1-85 GPU
    Driver.Version.: OpenCL 3.0 QUALCOMM build: commit unknown Compiler DX.17.75.00

Any help would be appreciated.
↧

Accell

January 4, 2025, 4:43 pm
$
0
0
Ive had acxell say 4096 and like 16000 but cant get it to only exact same instance
↧
↧

Ethereum Preseale Wallet: Token length exception

January 5, 2025, 7:10 am
$
0
0
Hey There,

I've got some free time on my hands and am looking back into cracking an Ethereum Pre-Sale Wallet a friend of mine lost the password for.  I could have swore I had hashcat working a year or two ago on this wallet but I'm a dummy that deleted all of my notes so I'm starting from scratch once more.

I've followed the good advice on this forum and several others to prepare my wallet hash (first using etherum2john.py, then just manipulating the hash manually into the format outlined by https://hashcat.net/wiki/doku.php?id=example_hashes).  A sample hash works, but mine always throws "Token length exception" before loading the CUDA kernel.

Comparing my wallet hash with the sample, the only thing I can see is that my bkp length is 64, not 32.  Actually cutting this down to 32 characters allows this to run but I'm sure trimming the value may result in different results and likely wasted compute effort.

Standard hash format:
Code:
$ethereum$w*<encseed:1248 characters>*<ethaddr:40 characters>*<bkp:32 characters>

My hash format:
Code:
$ethereum$w*<encseed:1248 characters>*<ethaddr:40 characters>*<bkp:64 characters>

After looking at the great write up of the BKP Field at:
https://www.reddit.com/r/ethereum/commen...on_file_a/

I haven't tried to generate anything and have the original JSON from the presale wallet.  The length of the BKP field is just longer than I suspect it should be, or I'm missing a flag in hashcat to allow for a longer format.

I'm wondering what next steps I should take.  Without the original seed value I don't think I can obtain the BKP.  I may be able to derive it, but would need the password and the original data.  I haven't jumped into the code for wallet type 16300 to see if the BKP value is used in the verification.... I'd like to think it is as it's being validated but throwing any value of length 32 seems to be acceptable which makes me think it is used as part of password validation.

Thanks in advance for any info someone may bring.
↧

Understanding performance of masks: test?a^6 vs. ?a^6test vs. ?a^6

January 7, 2025, 2:09 am
$
0
0
Hey there,

on the same hardware

?a?a?a?a?a?a --- takes ~ 10 Sek at > 70 GH/s
?a?a?a?a?a?atest --- takes ~ 10 Sek at > 70 GH/s
test?a?a?a?a?a?a --- takes about 25 Min at only ~ 500 MH/s

why is it so slow if a prefix is known? It is more common to know a prefix than a suffix, isn't it? - at least that is what I observed.
-S does not improve the performance (it even slows it down quite a lot)

Thanks
↧

m16200 doesnt work

January 7, 2025, 5:23 am
$
0
0
hi, i am extracting this hash, can you help me how to parse it?
the thing is that hashcat doesn't understand it

  "hash_string": "$ASN$*1*0*500C3423399D076197EBFBAA10466661*1EEFCFCB627604FF28B5AC5E61683C41",
  "hash_type": 16200,
  "hwnd": 396224,
↧
Search

Hashcat wrong Hash "Veracrypt loader damaged"

January 8, 2025, 12:02 am
$
0
0
Hello,

i want to brute my own HDD.
When i get the hash with DD Hashcat says "no hash loaded"
so i looked into the hash file and it does not look normal, it looks like normal but it also says "veracrypt loader damaged, use rescue disk"

I tested it with a USB-Stick and same dd command, i get an valid hash.

I also send the HDD to a big company because i thought the HDD is damaged, but its not damaged.
So what could be the problem? is it just a format problem?

Hopefully someone can help me.

got the hash with sudo dd if=/dev/sdb of=disk bs=512 count=1

regards
↧
↧

Got tired looking for benchmarks, so I made all of them :D

January 9, 2025, 11:00 am
$
0
0
Hi guys, I've had lots of trouble finding benchmarks for some GPU models, especially full benchmarks on latest versions of hashcat, so I decided to benchmark as much GPUs as possible and put it all in one place for you to see: https://github.com/its5Q/hashcat-benchmarks

If you have a GPU that is not in this repo, I'd appreciate your contributions of full benchmarks! Enjoy!
↧

Long unknown password lenght

January 9, 2025, 3:04 pm
$
0
0
Hi everyone,

I'm extremely new to password cracking, however I have an encrypted file that I must recover as it has very important family pictures. 
Here's what I know:

Password is long, but exact length is unknown, possibly between 30-50 characters.
I know it uses various combinations of passwords I've used in the past, it uses 15-20 character long passwords in duplicate and then the rest is a combination of blocks of 4, 2 or 1 of a select known few numbers and characters.

I've made a wordlist with all possible passwords that are included in the ending password, but how do I make hashcat try more combinations with them.

Let's say I have a word list like:

Example1
Example2
Example3
Example4
[and so on]
Example 130
Example 131


What attack exactly would make hashcat try all of these inputs combined up to a max of lets say 8 inputs pooled together including wordlist input repetitions like for example it would try a combination like:

Example1Example55Example62Example55Example41Example32Example85Example77

but also include shorter pooled combinations like

Example44Example7Example32

Sorry if this post seems basic, just putting things into terms I'm comfortable with.

Currently the line im running (to exhaustion) is

hashcat -m 13721 -a 1 -w 4 C:\Users\USERNAME\Desktop\target\target_hash.tc C:\Users\USERNAME\Desktop\wordlist1.txt C:\Users\USERNAME\Desktop\wordlist2.txt 

Any help would be appreciated, if possible in a straightforward and easy way for a beginner to understand.

Thank you all for reading!
↧

Electrum 1 Hash: Token length exception

January 9, 2025, 5:24 pm
$
0
0
I'm trying to run an attack on the sample Electrum  hash provided in the documentation:

$electrum$2*7f4cbaa104234efd9f09eefcfd35abb2*2ff6948067557572c6eb837af5302fef

I am trying with the following commands, but receiving a Token Length Exception

$ hashcat -a 3 -m 0  $electrum$2*7f4cbaa104234efd9f09eefcfd35abb2*2ff6948067557572c6eb837af5302fef


 $ hashcat -a 3 -m 16600  $electrum$2*7f4cbaa104234efd9f09eefcfd35abb2*2ff6948067557572c6eb837af5302fef


Interestingly, if I include only the first half of the hash or the last half of the hash (separated by the "*"), hashcat starts running

Can anyone suggest the right way to run an attack on this hash? Thanks in advance

hashcat -a 0 -m 16600  $electrum$2*7f4cbaa104234efd9f09eefcfd35abb2*2ff6948067557572c6eb837af5302fef
hashcat (v6.2.6-851-g6716447df) starting

Successfully initialized the NVIDIA main driver CUDA runtime library.

Failed to initialize NVIDIA RTC library.

* Device #1: CUDA SDK Toolkit not installed or incorrectly installed.
            CUDA SDK Toolkit required for proper device support and utilization.
            For more information, see: https://hashcat.net/faq/wrongdriver
            Falling back to OpenCL runtime.

nvmlDeviceGetFanSpeed(): Not Supported

OpenCL API (OpenCL 3.0 CUDA 12.6.65) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #1: NVIDIA GeForce RTX 4060 Laptop GPU, 7680/7836 MB (1959 MB allocatable), 24MCU

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256

Hash '*7f4cbaa104234efd9f09eefcfd35abb2*2ff6948067557572c6eb837af5302fef': Token length exception

* Token length exception: 1/1 hashes
 This error happens if the wrong hash type is specified, if the hashes are
 malformed, or if input is otherwise not as expected (for example, if the
 --username or --dynamic-x option is used but no username or dynamic-tag is present)

No hashes loaded.

Started: Thu Jan  9 20:30:58 2025
Stopped: Thu Jan  9 20:31:00 2025
↧

Modernize hashcat

January 10, 2025, 9:55 am
$
0
0
Will there be new version accepting AMD CPUs like 9950X(3D) or nVidia RTX 4090 cards (both CUDA and OpenCL)?

Can hashcat be polished to use these hardware? And when?
↧
↧

AMD 760M BENCH WPA2 ON THINKPAD P14S GEN5 AMD

January 10, 2025, 1:23 pm
$
0
0
OpenCL API (OpenCL 2.1 AMD-APP (3584.0)) - Platform #1 [Advanced Micro Devices, Inc.]
=====================================================================================
* Device #1: AMD Radeon 760M Graphics, 8480/17087 MB (3780 MB allocatable), 4MCU

Benchmark relevant options:
===========================
* --optimized-kernel-enable

The plugin 2500 is deprecated and was replaced with plugin 22000. For more details, please read: https://hashcat.net/forum/thread-10253.html

------------------------------------------------------
* Hash-Mode 2500 (WPA-EAPOL-PBKDF2) [Iterations: 4095]
------------------------------------------------------

Speed.#1.........:  121.9 kH/s (63.76ms) @ Accel:128 Loops:512 Thr:128 Vec:1

Started: Fri Jan 10 22:20:29 2025
Stopped: Fri Jan 10 22:20:36 2025

C:\Users\Home\Desktop\HASHCAT GG\hashcat-6.2.6>pause
Appuyez sur une touche pour continuer...
↧

Hashcat/Nvidia Issues

January 10, 2025, 2:34 pm
$
0
0
I'm having issues to use hashcat, as it always return me the following error:

Code:
nvmlDeviceGetFanSpeed(): Not Supported

CUDA API (CUDA 12.4)
====================
* Device #1: NVIDIA GeForce RTX 2080 with Max-Q Design, 7854/7967 MB, 46MCU

OpenCL API (OpenCL 3.0 CUDA 12.4.131) - Platform #1 [NVIDIA Corporation]
========================================================================
* Device #2: NVIDIA GeForce RTX 2080 with Max-Q Design, skipped

Benchmark relevant options:
===========================
* --optimized-kernel-enable

-------------------
* Hash-Mode 0 (MD5)
-------------------

cuLinkAddData(): the provided PTX was compiled with an unsupported toolchain.

* Device #1: Kernel /usr/share/hashcat/OpenCL/shared.cl link failed. Error Log:

ptxas application ptx input, line 9; fatal  : Unsupported .version 8.5; current version is '8.4'



* Device #1: Kernel /usr/share/hashcat/OpenCL/shared.cl build failed.

So far I've tried reinstalling both Cuda and Nvidia drivers, using different versions, searching in different places on methods of install, and no success. I'm currently using the latest available hashcat version (6.2.6).

Here's the output from nvidia-smi and cuda version:

Code:
$ sudo pacman -Q | grep hashcat
hashcat 1:6.2.6-2
$ sudo pacman -Q | grep cuda
cuda 12.6.3-1
$ nvidia-smi
Fri Jan 10 19:28:07 2025     
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.142                Driver Version: 550.142        CUDA Version: 12.4    |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf          Pwr:Usage/Cap |          Memory-Usage | GPU-Util  Compute M. |
|                                        |                        |              MIG M. |
|=========================================+========================+======================|
|  0  NVIDIA GeForce RTX 2080 ...    Off |  00000000:01:00.0 Off |                  N/A |
| N/A  57C    P0            16W /  90W |      1MiB /  8192MiB |      0%      Default |
|                                        |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
                                                                                       
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU  GI  CI        PID  Type  Process name                              GPU Memory |
|        ID  ID                                                              Usage      |
|=========================================================================================|
|  No running processes found                                                            |
+-----------------------------------------------------------------------------------------+

Finally, here's my system specifications:

Code:
OS: Manjaro 24.1.2 Xahea
Kernel: x86_64 Linux 6.6.54-2-MANJARO
DE: GNOME 46.4
CPU: Intel Core i7-8750H @ 12x 4.1GHz [74.0°C]
GPU: NVIDIA GeForce RTX 2080 with Max-Q Design

Feel free to ask for any relevant information needed to solve this issue.
↧
Search

Hashcat mode 11300 compatibility with Bitcoin Core v169900 SQLite descriptor wallets?

January 11, 2025, 6:05 am
$
0
0
I'm trying to use hashcat mode 11300 with a newer Bitcoin Core wallet (version 169900) that uses SQLite format with descriptors enabled.

Current wallet info: - walletversion: 169900 - format: sqlite - descriptors: true

I've extracted the following data:
mkey: 
salt:
iterations:

When trying various hash formats, I consistently get either "Separator unmatched" or "Salt-value exception" errors.

Questions:
1. Does mode 11300 support newer SQLite-based descriptor wallets?
2. If yes, what's the correct hash format for these newer wallets?
3. If no, are there plans to add support for newer wallet formats?

Running hashcat v6.2.5 on Ubuntu with CUDA 12.6
↧

AMD 760M BENCHMARK

January 12, 2025, 8:57 am
$
0
0
C:\Users\Home\Desktop\hashcat-6.2.6\hashcat-6.2.6>hashcat.exe -b -w 3
hashcat (v6.2.6) starting in benchmark mode

hiprtcCompileProgram is missing from HIPRTC shared library.

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

ADL2_Overdrive_Caps(): -8

OpenCL API (OpenCL 2.1 AMD-APP (3584.0)) - Platform #1 [Advanced Micro Devices, Inc.]
=====================================================================================
* Device #1: AMD Radeon 760M Graphics, 8480/17087 MB (3780 MB allocatable), 4MCU

Benchmark relevant options:
===========================
* --workload-profile=3

-------------------
* Hash-Mode 0 (MD5)
-------------------

Speed.#1.........:  2010.5 MH/s (64.75ms) @ Accel:2048 Loops:512 Thr:32 Vec:1

----------------------
* Hash-Mode 100 (SHA1)
----------------------

Speed.#1.........:  1472.5 MH/s (88.91ms) @ Accel:1024 Loops:1024 Thr:32 Vec:1

---------------------------
* Hash-Mode 1400 (SHA2-256)
---------------------------

Speed.#1.........:  736.0 MH/s (88.81ms) @ Accel:256 Loops:1024 Thr:64 Vec:1

---------------------------
* Hash-Mode 1700 (SHA2-512)
---------------------------

Speed.#1.........:  213.7 MH/s (76.17ms) @ Accel:16 Loops:1024 Thr:256 Vec:1

-------------------------------------------------------------
* Hash-Mode 22000 (WPA-PBKDF2-PMKID+EAPOL) [Iterations: 4095]
-------------------------------------------------------------

Speed.#1.........:  111.3 kH/s (64.79ms) @ Accel:64 Loops:512 Thr:256 Vec:1

-----------------------
* Hash-Mode 1000 (NTLM)
-----------------------

Speed.#1.........:  1482.6 MH/s (88.16ms) @ Accel:1024 Loops:1024 Thr:32 Vec:1

---------------------
* Hash-Mode 3000 (LM)
---------------------

Speed.#1.........:  5382.2 MH/s (96.82ms) @ Accel:1024 Loops:1024 Thr:128 Vec:1

--------------------------------------------
* Hash-Mode 5500 (NetNTLMv1 / NetNTLMv1+ESS)
--------------------------------------------

Speed.#1.........:  1415.7 MH/s (45.77ms) @ Accel:4096 Loops:128 Thr:32 Vec:1

----------------------------
* Hash-Mode 5600 (NetNTLMv2)
----------------------------

Speed.#1.........:  219.6 MH/s (74.82ms) @ Accel:64 Loops:1024 Thr:64 Vec:1

--------------------------------------------------------
* Hash-Mode 1500 (descrypt, DES (Unix), Traditional DES)
--------------------------------------------------------

Speed.#1.........:  143.3 MH/s (56.91ms) @ Accel:64 Loops:1024 Thr:32 Vec:1

------------------------------------------------------------------------------
* Hash-Mode 500 (md5crypt, MD5 (Unix), Cisco-IOS $1$ (MD5)) [Iterations: 1000]
------------------------------------------------------------------------------

Speed.#1.........:  798.7 kH/s (63.74ms) @ Accel:256 Loops:1000 Thr:64 Vec:1

----------------------------------------------------------------
* Hash-Mode 3200 (bcrypt $2*$, Blowfish (Unix)) [Iterations: 32]
----------------------------------------------------------------

Speed.#1.........:    6453 H/s (69.10ms) @ Accel:8 Loops:32 Thr:16 Vec:1

--------------------------------------------------------------------
* Hash-Mode 1800 (sha512crypt $6$, SHA512 (Unix)) [Iterations: 5000]
--------------------------------------------------------------------

Speed.#1.........:    11695 H/s (66.16ms) @ Accel:16 Loops:1024 Thr:256 Vec:1

--------------------------------------------------------
* Hash-Mode 7500 (Kerberos 5, etype 23, AS-REQ Pre-Auth)
--------------------------------------------------------

Speed.#1.........:  104.7 MH/s (79.07ms) @ Accel:512 Loops:128 Thr:32 Vec:1

-------------------------------------------------
* Hash-Mode 13100 (Kerberos 5, etype 23, TGS-REP)
-------------------------------------------------

Speed.#1.........:  102.6 MH/s (80.44ms) @ Accel:256 Loops:256 Thr:32 Vec:1

---------------------------------------------------------------------------------
* Hash-Mode 15300 (DPAPI masterkey file v1 (context 1 and 2)) [Iterations: 23999]
---------------------------------------------------------------------------------

Speed.#1.........:    20894 H/s (65.54ms) @ Accel:512 Loops:256 Thr:64 Vec:1

---------------------------------------------------------------------------------
* Hash-Mode 15900 (DPAPI masterkey file v2 (context 1 and 2)) [Iterations: 12899]
---------------------------------------------------------------------------------

Speed.#1.........:    8807 H/s (72.04ms) @ Accel:64 Loops:128 Thr:256 Vec:1

------------------------------------------------------------------
* Hash-Mode 7100 (macOS v10.8+ (PBKDF2-SHA512)) [Iterations: 1023]
------------------------------------------------------------------

Speed.#1.........:    91709 H/s (46.94ms) @ Accel:16 Loops:511 Thr:256 Vec:1

---------------------------------------------
* Hash-Mode 11600 (7-Zip) [Iterations: 16384]
---------------------------------------------

Speed.#1.........:    29636 H/s (66.26ms) @ Accel:256 Loops:1024 Thr:32 Vec:1

------------------------------------------------
* Hash-Mode 12500 (RAR3-hp) [Iterations: 262144]
------------------------------------------------

Speed.#1.........:    5460 H/s (91.06ms) @ Accel:32 Loops:16384 Thr:64 Vec:1

--------------------------------------------
* Hash-Mode 13000 (RAR5) [Iterations: 32799]
--------------------------------------------

Speed.#1.........:    11805 H/s (84.97ms) @ Accel:64 Loops:512 Thr:256 Vec:1

--------------------------------------------------------------------------------
* Hash-Mode 6211 (TrueCrypt RIPEMD160 + XTS 512 bit (legacy)) [Iterations: 1999]
--------------------------------------------------------------------------------

Speed.#1.........:    68541 H/s (52.86ms) @ Accel:64 Loops:256 Thr:128 Vec:1

-----------------------------------------------------------------------------------
* Hash-Mode 13400 (KeePass 1 (AES/Twofish) and KeePass 2 (AES)) [Iterations: 24569]
-----------------------------------------------------------------------------------

Speed.#1.........:    11923 H/s (55.92ms) @ Accel:128 Loops:512 Thr:64 Vec:1

----------------------------------------------------------------
* Hash-Mode 6800 (LastPass + LastPass sniffed) [Iterations: 499]
----------------------------------------------------------------

Speed.#1.........:  649.4 kH/s (76.84ms) @ Accel:512 Loops:499 Thr:32 Vec:1

--------------------------------------------------------------------
* Hash-Mode 11300 (Bitcoin/Litecoin wallet.dat) [Iterations: 200459]
--------------------------------------------------------------------

Speed.#1.........:    1183 H/s (69.26ms) @ Accel:64 Loops:1024 Thr:64 Vec:1

Started: Sun Jan 12 17:52:12 2025
Stopped: Sun Jan 12 17:54:32 2025

C:\Users\Home\Desktop\hashcat-6.2.6\hashcat-6.2.6>pause
Appuyez sur une touche pour continuer...
↧
↧

[Benchmark] Radeon 7900 XTX

January 12, 2025, 1:36 pm
↧

[Benchmark] Radeon VII

January 12, 2025, 1:38 pm
↧

Retrieving back digital assets that were lost to a fraudulent platform.

January 12, 2025, 5:09 pm
$
0
0
I am Michael. I saw an advertisement discussing how profitable Ethereum and USDT may be when the rate spikes. Since Ethereum has a lot of promise and I have high hopes for the reward that will accompany it, I have put all of my money into it and am waiting for it to develop even more. A few years later, it had produced more profit, and I was prepared to withdraw my money when the problem arose. I became really anxious and had to try every potential solution without success. I stumbled over an article one day while looking around the internet about how Supreme Peregrine Recovery had aided in their recuperation. Digital assets were lost. I muster the bravery to get in touch with them and tell them all that has transpired over the years, collaborating with their experts at every turn. They assist me in getting all of my digital assets back from the fraudulent investment platform. Even though it seems impossible, they managed to complete the assignment without any problems. Get all of your lost digital assets quickly by getting in touch with Supreme Peregrine Recovery right now.

Whatsapp: +1,8,7,0,2,2,6,0,6,5,9
Email:  supremeperegrinerecovery567(@)zohomail(.)com
supremeperegrinerecovery(@)proton(.)me
URL: supremeperegrinerecovery(.)com

.jpg   518744de-9c3d-43b7-9d5d-d61b1e04072c.jpg (Size: 115.56 KB / Downloads: 1)
↧
Viewing all 8224 articles
Browse latest View live
Search