CodeScoring Launches CodeScoring.Save Artifact Repository for Secure Enterprise Development
CodeScoring has unveiled its own artifact repository, CodeScoring.Save, aimed at organizations that need a reliable, on-premises solution for storing and distributing software packages, libraries, container images, and other development components.
The new product is positioned for the corporate segment and companies of any scale that require a predictable and fault-tolerant artifact repository. According to Dmitry Klyuchnikov, head of product development at CodeScoring, the solution was developed in the Go language with a focus on modern Kubernetes environments and secure development standards.
Save belongs to the same category as Sonatype Nexus Repository, JFrog Artifactory, and Harbor. It ships with an automated migration tool from public repositories and supports simultaneous hosting of internal artifacts and proxying of external ones. The repository offers native support for Maven, npm, NuGet, PyPI, Go Modules, Docker/OCI, DEB, RPM, and raw files.
Deployed via Helm in Kubernetes, the system includes role-based access control, dedicated accounts for automation, system and user activity auditing, and a REST API. Compute and storage layers are separated to allow independent scaling.
A key architectural feature is built-in security integration: CodeScoring.Save connects directly with CodeScoring.OSA so that vulnerability information can be viewed inside the repository. The company stresses that Save remains a fully independent product that can be purchased with or without the main CodeScoring platform.
While OSA Proxy validates incoming packages against security policies, Save focuses on storage and distribution. Their integration creates a single trusted entry point that prevents malicious components from entering the development environment. CodeScoring also plans to extend Save to handle AI models, beginning with storage and distribution capabilities for platforms such as Hugging Face, and intends to pursue certification aligned with Russian secure development requirements.
Related articles
Anthropic Funds New Security Developer Role at Python Software Foundation Following Sharp Rise in Vulnerabilities
Anthropic has financed a new security position within the Python Software Foundation in response to a marked increase in vulnerabilities and malicious packages affecting the Python ecosystem. Data published by Seth Larson showed a significant spike in reported issues during 2026. Brett Smith has been appointed as Security Developer and will collaborate with Larson, who serves as Security Developer-in-Residence, and Mike Fiedler, the PyPI security engineer. The expanded team will focus on scaling automated quarantine mechanisms in PyPI and streamlining the workflows of the Python Security Response Team. At PyCon US 2026, the team reported handling three to four times more vulnerability disclosures for Python and pip compared with the previous year, alongside a 60 percent increase in malware detections and removals from the repository.
Malicious ZIP Archive Delivers Git-Based Remote Code Execution via Hooks and Filters
A developer received a fake job offer from Cryptic Heaven through LinkedIn, leading to a ZIP file containing a rigged Git repository. The archive included a pre-configured .git directory with altered hooksPath pointing to .git/objects/interrupt and a custom clean filter named ltr. Upon git status or branch checkout, the setup triggered a shell script that downloaded and executed remote code from a server hosted on vercelscript.vercel.app. The attack leveraged post-checkout hooks and Git filters to run silently without requiring install scripts or explicit execution. Multiple trigger paths existed, including automatic detection in Visual Studio Code, Git-aware terminal prompts, and following README instructions to switch branches. The technique worked on both Linux/macOS and Windows through Git for Windows shell support. The incident highlights risks of opening untrusted Git repositories delivered outside standard clone workflows.
OIDC-Based Push Deployment on VPS Removes SSH Keys from CI While Enforcing Strict Isolation
A new self-hosted deployment system called cd enables secure continuous delivery to single Linux VPS hosts running Docker without storing any long-lived secrets in CI repositories. The architecture relies on short-lived OIDC JWT tokens issued by GitHub Actions or GitLab CI, verified on the target server through JWKS public keys. The server component cdd performs token validation, archive checks, resource-limited builds inside BuildKit, health checks, and automatic rollback on failure. All containers are launched with read-only root filesystems, dropped capabilities, no-new-privileges, and network binding restricted to 127.0.0.1 behind Caddy or Nginx. Administrative control is provided by the cdctl CLI that registers projects, sets RAM/CPU limits, and manages DNS records via Porkbun integration. The entire solution avoids external databases, web panels, and persistent secrets while enforcing one-repository-to-one-application boundaries.
Stolen Credentials Poison cPGuard Update Channel, Turning Security Software into Data Theft Backdoor
Attackers used compromised OPSSHIELD credentials to hijack the cPGuard update distribution network on November 2 at 02:06 UTC, injecting malicious scripts into versions 5.88.12 through 5.88.19. The poisoned updates targeted Linux servers running the security tool, which holds root privileges on hosting provider and cloud infrastructure machines. The script harvested /etc/shadow, /etc/passwd, MariaDB/MySQL root credentials from my.cnf, root shell history containing API tokens, and SSH authorized_keys files before exfiltrating them via the vendor's own infrastructure. A persistent backdoor was also dropped at /var/tmp/.cpg91511_sh. OPSSHIELD detected the intrusion within 12 hours and halted distribution, but confirmed that 32 customer servers had their data accessed. The incident highlights risks of relying on static credentials for security product update pipelines without code signing or behavioral restrictions.