ADscan v2.2.1

TL;DR

• Idempotent installs: fixes when pyenv or BloodHound CE were already present.

• No more CLI collisions: resolves bloodhound-cli name clash with SpecterOps’ tool and ensures the custom bloodhound-cli is upgraded correctly.

• Security & hygiene: automated BH CE password change during adscan install + isolated venvs for all external tools.

• After upgrade, run: adscan install.

---

🛠 Fixes

• pyenv: fixed installer error when pyenv was already installed. 🔺 🔗

• BloodHound CE: fixed installer error when BH CE was already installed. 🔺

• CLI collision: fixed bloodhound-cli name conflict with SpecterOps’ binary vs. ADscan’s custom script. 🔺 🔗

• Custom CLI updates: fixed custom bloodhound-cli not upgrading during adscan install. 🔺 🔗

⬆️ Improvements

• Automated BH CE password rotation in adscan install (no manual prompts). ⏫ 🔗

• Per-tool isolated virtualenvs for all external tools (cleaner deps, fewer conflicts). 🔼 🔗

---

⚠️ Action after upgrading

Run the toolchain refresh to apply venv isolation & BH CE changes:

pipx upgrade adscan adscan install adscan check

---

🧭 Notes

• If you previously had SpecterOps’ bloodhound-cli on PATH, adscan install now resolves the collision and ensures ADscan’s custom bloodhound-cli is reachable and upgraded.

• Isolated venvs may change where dependencies live; use adscan check to verify environment health.

---

📣 Feedback / Issues

If something breaks or you spot a regression, open an issue with a redacted log plus your distro and ADscan version.