Skip to content

test: keep tracked files clear of malware-scanner signatures - #43

Open
vkosuri wants to merge 1 commit into
mainfrom
chore/scanner-strings
Open

vkosuri wants to merge 1 commit into
mainfrom
chore/scanner-strings

Conversation

@vkosuri

@vkosuri vkosuri commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

The vahinitech.com server runs maldet nightly over home folders and /tmp. It flagged our own test payloads in other repositories on 2026-10-16, and on 2026-10-19 found one in a .pyc: the source split it with +, but Python folds two literals into one constant when it compiles.

  • No tracked file here matches today (checked by file name and signature only, against maldet's 2,296 literal signatures).
  • tests/test_scanner_strings.py keeps it that way: every tracked file and name, the constants of every compiled .py, and maldet's hex.dat when it is readable (VAHINI_MALDET_SIGS=none skips that part). Two self-tests show it catches a joined payload and a folded one.
  • AGENTS.md (Security) carries the short rule and links to the shared skill in vahinitech/Umbrella#16.

Checked locally: pytest tests/test_scanner_strings.py 4 passed; black --check clean; pylint on the file rated 9.46 with only the missing-pytest import error of the bare tool environment.

🤖 Generated with Claude Code

The server's nightly maldet scan flagged test payloads in other Vahini
repositories on 2026-10-16 and, through a constant-folded .pyc, on
2026-10-19. Nothing in this repository matches today; the new test keeps
it that way by checking every tracked file and name, the constants of
every compiled .py, and maldet's own signatures when hex.dat is readable.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant