# Security Baked Into the JVM: the Safe Codebase Audit Pipeline

DevFeed: [Security Baked Into the JVM: the Safe Codebase Audit Pipeline](<https://devfeed.tech/articles/security-baked-into-the-jvm-the-safe-codebase-audit-pipeline-18929.md>)

Original publisher: [Read original article](<https://blog.frankel.ch/security-baked-into-jvm/2/>)

Author: Peter Firmstone

Published: 2026-07-19T00:00:00Z

Content type: article

Language: en

Sources: [Nicolas Fränkel](<https://devfeed.tech/sources/nicolas-frankel.md>)

Topics: [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Data serialization](<https://devfeed.tech/topics/data-serialization.md>)

Tags: [audit](<https://devfeed.tech/tags/audit.md>), [bytecode](<https://devfeed.tech/tags/bytecode.md>), [dirtychai](<https://devfeed.tech/tags/dirtychai.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [java](<https://devfeed.tech/tags/java.md>), [jgdms](<https://devfeed.tech/tags/jgdms.md>), [jini](<https://devfeed.tech/tags/jini.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [security](<https://devfeed.tech/tags/security.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [supply-chain-compromise](<https://devfeed.tech/tags/supply-chain-compromise.md>), [technical](<https://devfeed.tech/tags/technical.md>)

## AI overview

The excerpt presents SCAP as a way to inspect third-party JARs before clients deserialize objects from them, addressing the risk that runtime-loaded code may be replaced with malicious bytecode. It identifies two targets: dangerous bytecode that can arrive through legitimate permission grants, and blocking static initializers that can stall virtual-thread scheduling. SCAP uses SHA-256 content hashes so a JAR is analyzed once regardless of which services serve it. The described architecture assigns separate roles to five hosts and limits network access; the excerpt specifies that the Lookup Service stores service items opaquely and emits registration events, while the Codebase Downloader alone has outbound internet access and proactively fetches JARs on those events. The excerpt cuts off before describing the remaining hosts.

## Source excerpt

In Part 1, the minimal deployment showed constraints traveling with the proxy: authentication, encryption, hardened deserialization, all declared in configuration and enforced at the call boundary. The proxy is a JAR. That JAR was downloaded and unmarshalled before any constraint ran. That step is the earlier problem. Distributed Java systems that load remote code are vulnerable to supply chain compromise: an attacker can replace a legitimate JAR with one containing malicious bytecode.