So I have doing this challenge tell me the answer ...

I’ll inspect the provided challenge files for challenge3.exe, then trace the final checksum check to extract the divisor and format it as requested.

I can solve it, but challenge3.exe isn’t attached here, and the private host 172.25.65.103 isn’t reachable from this environment.

Upload challenge3.exe and I’ll inspect the final checksum-validation routine and return just the hexadecimal divisor in the required NxNX format.

I checked the supplied Challenge 48 lab evidence. In TKT-TKT-004_Emergency_Staging.md, the ticket shows:

• Region | North Ridge
• Maria — North Ridge

Challenge 48 answer: North Ridge

I checked the Challenge 48 evidence across the files you sent.

The decisive file is TKT-TKT-004_Emergency_Staging.md, which contains:

Region | North Ridge

and under Personnel:

Maria — North Ridge

So the answer in the required Xxxxx Xxxxx format is:

North Ridge

One important detail: in CPENT-Evidence-All.zip, the Challenge 48 retrieval attempts show HTTP 000 and the saved answer/data files are empty. The explicit North Ridge value comes from the earlier C48-V3-CPENT-Style-Practice-Lab.zip you supplied. If that ZIP is a faithful copy of your target evidence, North Ridge is the answer.

I audited the evidence inside your IOT.zip, including the DOCX reports and the supporting screenshots. Your technical work is mostly solid, but there are two answers I would change before submitting, plus two challenges where the stated answer-format template conflicts with the actual evidence.

Final audit

The two answers you should definitely fix

Challenge 17

Your report currently ends up with:

Dx82x32C

I would not submit that.

Your own screenshot proves:

text
14164780    0xD8232C    xz compressed data

You also independently ran:

text
printf '0x%x\n' 14164780

and obtained:

text
0xd8232c

Therefore the actual offset is unequivocally:

0xD8232C

Dx82x32C was created by artificially rearranging the value to imitate the provided format. An offset should never be rewritten that way.

Challenge 17: 0xD8232C

The displayed NxNNxNNN template itself appears inconsistent with the hexadecimal offset. The natural format for this answer would have been something like NxXNNNxX for 0xD8232C.

Challenge 19

Your evidence contains the BusyBox string:

text
BusyBox v1.21.1--LSDK-10.2-00082-4

Your report currently reduces this to:

1.21.1

Technically that is the numerical BusyBox version, but look carefully at the challenge's required format:

text
xN.NN.N

That precisely matches:

text
v1.21.1

• v = lowercase character
• 1
• .
• 21
• .
• 1

So for the actual answer field, I would use:

Challenge 19: v1.21.1

This is one of the most important corrections in your set.

Challenge 16 — your evidence is right, but the format looks wrong

You proved that offset 0x813682 begins with:

text
FD 37 7A 58 5A 00

That is the XZ magic signature.

Binwalk also reports:

text
8468098    0x813682    xz compressed data

So the file format is unquestionably:

XZ

The problem is that the question says:

text
Answer format: XXX

which implies three uppercase letters. There is no legitimate reason to turn XZ into a made-up three-character answer.

Do not submit things such as XZZ, XZC, etc.

Challenge 16: XZ

I would treat the XXX template as a likely formatting mistake in the challenge.

Challenge 25 — evidence strongly supports WNDR3800

Your screenshot contains many explicit strings such as:

text
NETGEAR Router WNDR3800

and your search directly returns:

text
WNDR3800

So the device identification is very strong:

WNDR3800

The only problem is the supplied format:

text
XXXXNXXX

WNDR3800 is actually:

text
XXXXNNNN
WNDR3800

Again, I would not modify the actual device model just to force it into a faulty template. Your evidence repeatedly identifies the model as WNDR3800.

Challenge 25: WNDR3800

Verification of the remaining answers

Challenge 13 — 65536 ✅
Your Binwalk evidence reports:

text
Squashfs filesystem
blocksize: 65536 bytes

Exactly five digits as required.

Challenge 14 — Blackfin ✅
The firmware is identified as:

text
Linux/Blackfin

And Blackfin matches Xxxxxxxx exactly.

Challenge 15 — Linux 2.6.26.5 ✅
The embedded kernel name is:

text
Linux-2.6.26.5-ADI-2009R1-pre-gd

The required format is satisfied exactly by:

Linux 2.6.26.5

Challenge 18 — 192.168.0.60 ✅
Your extracted database evidence associates DSP-W215 with:

192.168.0.60

It also exactly matches NNN.NNN.N.NN.

Challenge 20 — 4.3.1 ✅
Your extracted kernel strings explicitly contain:

text
gcc version 4.3.1

So:

4.3.1

Challenge 21 — JFFS2 ✅
Binwalk reports:

text
7077888  0x6C0000  JFFS2 filesystem, little endian

JFFS2 perfectly matches XXXXN.

Challenge 22 — 7754752 ✅
stat -c '%s' FileOne.bin produced:

text
7754752

Exactly seven digits.

Challenge 23 — 0xE0080 ✅
Binwalk reports:

text
917632    0xE0080    Squashfs filesystem

This one is particularly nice because it matches the requested format exactly:

text
N x X NNNN
0 x E 0080

So:

0xE0080

Challenge 24 — passwd ✅
Your extracted IOT6 filesystem includes the credential hash in the passwd file. Your screenshot shows an entry such as:

text
admin:$1$...:0:0:root:/:/bin/sh

So passwd is consistent with both the evidence and the six-lowercase-character answer format.

Submission list I recommend

text
Challenge 13: 65536
Challenge 14: Blackfin
Challenge 15: Linux 2.6.26.5
Challenge 16: XZ
Challenge 17: 0xD8232C
Challenge 18: 192.168.0.60
Challenge 19: v1.21.1
Challenge 20: 4.3.1
Challenge 21: JFFS2
Challenge 22: 7754752
Challenge 23: 0xE0080
Challenge 24: passwd
Challenge 25: WNDR3800

So the main takeaway is: change Challenge 17 from Dx82x32C → 0xD8232C, and Challenge 19 from 1.21.1 → v1.21.1. Challenges 16 and 25 have strong evidence for your answers, but the answer-format strings supplied in the question appear inconsistent with those values.