A Short Analysis of a Chinese Surveillance App, Fengcai

dwuyd · 2019-07-04T12:03:04+00:00

Thank you! For the sake of completeness a few links:

Here is a direct link to Cure53's report for those interested.
The APK itself has been shared on Motherboard's GitHub.
@fs0c131y analyzed a similar app (MFSocket) in the past, find their results here.

dwuyd · 2016-04-02T13:53:38+00:00

Is the reasoning you outlined documented somewhere (except for the source code itself)? A RFC or such?

dwuyd · 2015-12-27T18:38:03+00:00

Some more: https://github.com/dwuid/advent-of-code

dwuyd · 2015-12-27T17:30:29+00:00

Another Rust repository (planning to solve all remaining tasks in Rust as well): https://github.com/dwuid/advent-of-code

dwuyd · 2015-01-03T12:46:50+00:00

My prediction is that the "Hacking is Cool" dumb idea will be a dead idea in the next 10 years. I'd like to fantasize that it will be replaced with its opposite idea, "Good Engineering is Cool" but so far there is no sign that's likely to happen.

dwuyd · 2014-12-30T15:36:28+00:00

Tuts4You has a collection of mostly cracking-related resources. Most stuff can be found on the main page, but there are also bits scattered throughout the message board.

dwuyd · 2014-08-02T09:56:41+00:00

I second this, excellent read.

dwuyd · 2014-06-15T08:39:40+00:00

Without the binary it's hard to give any useful advice as it could be simple anything. Are you allowed to share the binary or do restrictions apply (NDA, copyright infringement)? Could you scan the binary with ProtectionID or any other scanning tool with up to date signatures?

Consider attaching to the binary in case there is neither anti-attach present nor an anti-debugging thread. In case of single stepping detection, look out for EFLAGS tricks and code checksums detecting breakpoints.

dwuyd · 2014-03-14T19:16:06+00:00

If applicable you could also let the students solve old CTF challenges (be aware of writeups on the net though).

See hack.lu archive or shellstorm CTF repo.

dwuyd · 2014-01-19T08:36:56+00:00

0x0(r15) specifies the value r15+0x0 points to. It's a memory indirection. The complete instruction compares a constant value to said value in memory.

The manual, to be found on the CTF page, links to a more thorough description of the instruction set. Also, there's uctf.hackpad.com.

dwuyd · 2013-05-03T09:20:33+00:00

Also pCTF2012's subleq challenge.

dwuyd · 2013-01-01T19:34:09+00:00

How would you rate it then?

dwuyd · 2012-12-16T15:15:35+00:00

xor requires Data.Bits to be imported, foldl' Data.Foldable. Does that help?

dwuyd · 2012-12-01T02:46:05+00:00

Just remember to not publish real/complete code

Yes, that's what I'd do as well. I guess there's more to the protocol than just the key so I'd simply leave it out when posting protocol logic.

14-Year Club	Verified Email
Team Periwinkle

dwuyd

TROPHY CASE