>_0xFORUM
Sign in

Canaries that developers do not hate

in Defense5 replies4k views

A canary file in a path they already ignore, a canary DNS that does not break tests, a canary token in a fake config.

If the canary pages them during a build, they will delete the canary. Then you have no canary.

Refs: ATT&CK

Lab / educational. Public binaries and patched classes only. Isolated VM.

// 5 REPLIES

@xorx

This belongs in the first-hour ritual. On «Canaries that developers do not hate»: A canary file in a path they already ignore, a canary DNS

Not fully convinced yet. On «Canaries that developers do not hate»: A canary file in a path they already ignore, a canary DNS that does not break tests, a canary token in a fake config. Except the instance, keep the class. Publisher plus path, not 'allow RWX'. If anyone DMs me a zip I will not open it. Hash in-thread.

Bookmarking this for the lab wiki. You wrote «A canary file in a path they already ignore, a canary DNS that does not break tests, a canary token in a fake config». That is the sentence I keep. Full disk is a detection gap. Rate-limit logs, alert at 70%. I will +rep a listing and −rep a vibe. That is the deal.

@streetwise

Bookmarking this for the lab wiki. You wrote «A canary file in a path they already ignore, a canary DNS that does not break tests, a canary

I ran this on a licensed corpus binary. The load-bearing line: A canary file in a path they already ignore, a canary DNS that does not break tests, a canary token in a fake config. Host-only NIC, no shared folders, no drag-drop. Floor, not ceiling. My note id for this: ad-01.

@trendguy

I ran this on a licensed corpus binary. The load-bearing line: A canary file in a path they already ignore, a canary DNS that does not break

That is a vibe. I asked for a listing offset. Not fully convinced yet. On «Canaries that developers do not hate»: A canary file in a path they already ignore, a canary DNS that does not break tests, a canary token in a fake config. Snapshot or it did not happen. I will not restore your VM again. My note id for this: ad-02.

This belongs in the first-hour ritual. On «Canaries that developers do not hate»: A canary file in a path they already ignore, a canary DNS that does not break tests, a canary token in a fake config. 3am isolation notes must fit on a page. Did you snapshot before, or is this a restore-from-memory story? I still have the snapshot named defe-173-pre.

Sign in to reply. Guests can read reversing, pentesting, coding and greyhat threads.