troupe allegedly hacked as reported by Everest ransomware with details: 1. aim AND scope This account describes the unified internal VIVOTEK data repository, including firmware, embedded-system images, source and build artifacts, SDKs, VADP, VCA and ANPR packages, NVR software, mill and service tools, documentation, diagnostic material and product-support data. The repository contains 94,837 files in 9,865 folders totaling 236.29 GB. The account covers the complete data localize in the VIVOTEK 1 and VIVOTEK 2 folders. All quantitative indicators, sizes, paths and descriptions pertain to the full contents of these two folders. The repository contains 338 top-level archive containers. Nested containers contain 8,461,670 file entries and 787,585 folder entries. Nested content is accounted for separately and is not added again to the file counting or total repository size. The data covers several generations of cameras and NVRs, internal development branches, exact SVN and Git manifests, the MD9560 source/build snapshot, arm and AArch64 development libraries, client SDKs, mill software, recovery environments, VADP applications, VCA, ANPR and engineering documentation. Values of passwords, keys, tokens and other sensitive parameters are not reproduced in this report. 2. MAIN FINDINGS The monument represents several generations of the VIVOTEK software platform rather than a single firmware release: - legacy ARM32 camera firmware and NVR software; - OneFW on HiSilicon with an exact SVN BOM; - an internal ARMv7 MD9560 build snapshot containing real C/C++ source, object files and dependency files; - AArch64 Ambarella CV2X and CV22 generations with internal development libraries and dwarf debug information; - a modern Git-based OneFW manifest covering 269 repositories with claim institutionalize SHA values; - CV22/SAV539 secure-boot and factory/provisioning packages; - a VADP, VCA and ANPR application ecosystem; - Windows node SDKs, media/viewing components and validation tooling; - NVR runtime, factory recovery environment and a native encrypted-image processing chain. key findings: 1. 53596_DResearch/9 - an internal MD9560 build snap with 109 VIVOTEK product C/C++ seed files, 873 .o files, 873 .d files, 613 headers and 133 built components. 2. Legacy OneFW manifest - 229 SVN components with exact revisions and repository paths. 3. Modern OneFW manifest - 269 git repositories with claim commit SHA values, branch and liberate label information. 4. 50084/v8 and 51494/v2 - AArch64 internal SDK/library builds with DWARF, source paths and exact toolchain information. 5. 83 source-based node and demonstration projects across VNDP, platform SDK, Fisheye and VitaminCtrl. 6. a broad ANPR integration pile and a substantial portion of VCA/VADP covering logic. 7. A readable legacy NVR root, a modern SigmaStar production/recovery surroundings and the element structure used to process encrypted NVR images. 8. mill Update program and validation cock packages with informative PDB files and internal source/build paths. Technical assessment: - the architecture of the main VIVOTEK generations and subsystems is substantially represented; - the node and integration layer is highly reproducible; - small VADP applications and a substantial part of orchestration/UI/configuration logic are reproducible; - selected MD9560 firmware modules can be partly rebuilt or relinked; - a complete clean build of the camera/NVR platform is not possible without the source repositories, nail toolchains/sysroots, kernel/BSP/bootloader source and release-signing environment. The engineering appraisal of repository coherence as a firmware, SDK, production and living resourcefulness is 95-97%. Functional reproducibility with available binaries and compatible hardware is 85-90%; for legacy cameras on corresponding hardware it is 90-95%. Application-level seed coverage is 35-50%, piece camera/NVR system-core source coverage is 10-20%. 3. REPOSITORY scale AND STRUCTURE Data tree | Files | Folders | Size | Top-level archives ------------------+----------+---------+-------------+------------------- VIVOTEK 1 | 90,135 | 8,686 | 128.05 gb | 123 VIVOTEK 2 | 4,702 | 1,179 | 108.24 gilbert | 215 total | 94,837 | 9,865 | 236.29 GB | 338 Nested package and image coverage: - 48,625 opened container instances across all nesting levels; - 8,461,670 file entries inside containers; - 787,585 folder entries inside containers; - 1,821,546 TAR link entries; - 6,640,124 non-link file entries; - 11,906 tracked package, image and archive roots; - 11,882 completed roots; - 24 partial roots; - 99.80% completed-root rate; - 61 legacy firmware or image objects requiring a specialized handler. The 99.80% figure describes the processing status of tracked roots. It does not mean that 99.80% of warhead content is readable, because some modern applications, firmware images and legacy image formats are protected or command platform-specific handling. The 236.29 gilbert figure is the tot stored repository size. Content inside nested archives is not added to it again. format | Files | size ------------------+-------+----------- ZIP | 151 | 4.18 gilbert TAR.GZ | 154 | 2.83 gilbert RAR | 15 | 656.33 megabyte secure TAR.GZ | 2 | 217.90 megabyte 7Z | 5 | 49.77 mb GZ | 1 | 26.86 mb TAR | 8 | 15.10 MB TGZ | 1 | 10.20 MB XZ | 1 | 7.82 mb total | 338 | 7.97 gilbert 3.1. FILE report BY format The table below lists formats with high stored volume and/or file count. The figures refer to files stored directly in the two data trees. Nested container contents are not added to these values. initialize | Files | size -------------------+--------+----------- .flash.pkg | 2,287 | 68.62 GB .img | 1,195 | 67.11 gigabyte .exe | 4,586 | 26.68 GB .dll | 52,314 | 25.54 GB .avi | 35 | 21.55 gilbert .tvs | 1 | 4.45 GB .zip | 151 | 4.18 gilbert .tar.gz | 154 | 2.83 GB .pkg | 53 | 1.43 gb .mp4 | 16 | 1.24 gigabit .rom | 85 | 1.18 GB No extension | 8,689 | 1.04 GB .pcm | 1,261 | 992.94 MB .mkv | 1 | 956.95 MB .xlsx | 287 | 856.97 mb .pdb | 118 | 845.22 megabyte .bmp | 88 | 797.68 mb .mov | 8 | 682.70 mb .rar | 15 | 656.33 MB .pdf | 274 | 565.37 MB .apk | 15 | 477.96 megabyte .wmv | 8 | 416.44 MB .dmp | 531 | 373.84 mb .sqfs | 10 | 273.97 megabyte .3gp | 1 | 270.90 MB .secure.tar.gz | 2 | 217.90 mb .bit | 1,596 | 210.91 MB .upt | 16 | 197.88 MB .wav | 516 | 192.59 megabyte .mp3 | 610 | 185.43 MB .xrc | 432 | 158.40 mb .bin | 251 | 120.95 megabyte .jpg | 1,068 | 108.87 megabyte .ncb | 19 | 101.43 MB .ipa | 2 | 88.16 MB .cab | 4 | 83.26 MB .msi | 1 | 82.82 mb .pch | 7 | 80.51 MB .ini | 9,021 | 69.57 MB .msg | 4 | 62.68 megabyte The two data trees also contain 136 CPP files, 179 C# files, 170 headers, 72 Visual Studio solvent files, 22 VC cast files, 50 C# project files, 95 shell scripts, 67 JavaScript files, 250 HTML files, 30 CSS files and 195 XML files. Nested source snapshots, SDKs and coating packages add C, C++, Python, CGI, shell, JavaScript, HTML, build files, headers and dependency material beyond these direct counts. 3.2. DEVELOPMENT coverage map development area | Represented material -------------------------------------------+------------------------------------------------------------- Legacy camera firmware | Readable packages, kernels, root images and install scripts legacy NVR multiplication | Kernel, ext2 root, services and Windows viewing components Internal MD9560 build | product source, objects, dependencies, headers and libraries OneFW subversion | 229 exact component revisions and repository paths OneFW Git | 269 exact repository commits, branches and liberate tag CV2X ramify | AArch64 headers, libraries, dwarf and project 50084/v8 CV22 fork | AArch64 headers, libraries, dwarf and externalise 51494/v2 modern camera firmware | Protected packages, poser configuration and boot metadata Client software | VNDP, platform SDK, Fisheye, VitaminCtrl and VAST2 VADP applications | Shell, CGI, JavaScript, Python, configuration and native encipher video analytics | VCA orchestration, protected analytics engines and packages ANPR | Runtime, regional data, UI, integrations and example records NVR recovery | U-Boot, UBI/UBIFS, kernel, NAND metadata and image utilities Factory software | product operate test Utility and Update program families proof software | Qt/QML ViewCell, media parsing, playback and trial functions Engineering material | Parts lists, ECN/DCN, sustenance and product-test media These areas are connected: source manifests define factor versions, build artifacts present compilation parameters, development bundles expose APIs, firmware packages contain runtime images, mould configuration defines services, mill tools program and corroborate dev
