Habr•September 18, 2026•🇷🇺Translated from Russian

NEOMSA ESB Release Strengthens Supply Chain Security Through SBOM and Dependency Hardening

NEOMSA ESB is a domestic on-premise integration platform based on Apache Camel and the Camel Karavan project. It provides a visual designer for integration routes while preserving the ability to edit generated YAML routes manually, store them in Git, and review them as code.

The platform includes a web-based designer, a Quarkus backend, a VS Code extension, and a catalog of components and Kamelets. It targets typical enterprise integration scenarios involving accounting, reporting, CRM, ERP, and industry-specific ABS/MES systems.

Why Dependency Composition Represents a Separate Risk Contour

An ESB acts as a central concentration point for data flows between processing systems, ERP, MES, CRM, anti-fraud, and regulatory reporting. Compromise of the bus therefore grants influence over the entire integration perimeter rather than a single application. Sensitive payment details and personal data transit through the bus memory even when they are not stored there.

Integration layers are deployed for years, while libraries age faster than platform releases. Apache Camel alone contains hundreds of components, so even limited usage results in a wide attack surface in the final build.

Automated Release Verification Process

Builds are fully automated. Every pipeline run performs the following steps:

  • Generation of an SBOM in CycloneDX format stored as a pipeline artifact.
  • SCA analysis using Grype on the SBOM and OWASP Dependency-Check on the repository tree, including frontend lock files.
  • SAST with SonarQube and Semgrep using offline rule sets.
  • Secret scanning with Gitleaks across the repository and commit history.
  • Aggregation of all findings into DefectDojo for deduplication and SLA tracking.

Images are built with Kaniko and tagged with the short commit hash, ensuring full traceability from artifact to source code.

Vulnerability Remediation Approach

The guiding rule is to raise each component only to the minimum version that resolves the reported advisory, not to the latest available release. This principle avoids unintended changes to default settings, function behavior, or removal of legacy methods.

For transitive dependencies, forced version overrides with exact pinning are applied. When multiple major branches of the same package coexist, overrides are defined separately for each branch.

Several non-trivial cases required manual engineering decisions:

  • postcss 7.x had no patch; the consuming resolve-url-loader package was upgraded, removing the vulnerable branch entirely.
  • The lodash advisory listed 4.17.23 as the last vulnerable version, yet 4.17.24 did not exist; after testing, 4.18.1 was selected following maintainer guidance against 4.18.0.
  • An update to a browser-support library altered compilation targets and broke a downstream package; the target set was adjusted to prevent the problematic transformation.
  • A lock file contained mismatched version, download URL, and checksum fields; a new verification step now checks all 5,866 lock-file entries for consistency.

Results and Platform Migration

After remediation the build showed zero Critical and High vulnerabilities. The remaining 59 Medium and 53 Low findings were documented in DefectDojo. Most belonged to build tools rather than runtime components.

Accumulated data demonstrated that point fixes had reached diminishing returns on the aging frontend build tooling. The team therefore migrated the fork to Camel Karavan 4.18, which uses Vite. The total package count dropped from 5,872 to 1,683, and the main interface contour shrank from 1,641 to 598 packages.

The same SBOM, scanning, and verification process continues for every build, ensuring the improved composition remains under control for customers.

Related articles

BoletimSec•Supply Chain & Open Source

Uber Breach Exposes 149,000 Drivers After Third-Party Vendor Credentials Stolen

Uber has notified approximately 149,346 drivers that personal data was stolen in an October incident involving a compromised third-party vendor. Attackers used valid credentials belonging to the vendor to access data the ride-hailing company had shared with it, bypassing all security alerts because the access appeared legitimate. The affected information includes driver license images, names, addresses, dates of birth and government-issued identification numbers. The vendor was later identified as Fireworks AI, a cloud platform for running and fine-tuning open-source AI models. The same credential theft campaign had previously impacted Notion and Cursor. Uber immediately severed the connection upon discovery, notified regulators in multiple U.S. states, and is offering credit monitoring to affected individuals.

BoletimSec•Supply Chain & Open Source

FBI Warns of ARTEX AI Pentest Framework Abused by Cybercriminals with Backdoored Docker Images

The FBI has issued an alert regarding the open-source ARTEX AI-powered penetration testing framework after it was observed in criminal operations targeting banks, governments, and technology companies since August 2026. Attackers achieved privileged access in under three hours in multiple incidents. The Cloud Security Alliance identified compromised Docker images containing a backdoor that executes root commands without authentication by exploiting a hidden CAPTCHA field value passed to sh -c. Approximately 9,000 downloads occurred from one malicious image, and 62 exposed consoles were found running the tampered version. Check Point reported 1,608 internet-exposed ARTEX consoles, including ten with exposed databases. The original GitHub repository was removed in October 2026, yet third-party copies and images continue to circulate. CERT-EU highlighted the lack of technical restrictions preventing out-of-scope actions by autonomous AI agents.

AntiMalware•Supply Chain & Open Source

Optimizely Supply Chain Attack Infects BBC, CNN, HSBC and 177 Other Sites with Crypto-Stealing JavaScript

On November 16, visitors to major corporate websites received malicious JavaScript that swapped cryptocurrency wallet addresses and attempted to intercept banking card data. The code was distributed through Optimizely Web, a platform used for A/B testing. Researchers identified the malicious code in 188 scripts belonging to 178 organizations, including BBC, CNN, Fox News, HSBC, Equifax, Zoom, Salesforce, GitLab and IKEA. Attacker Scott Helm from Report URI reconstructed the attack timeline: adversaries modified the Project JavaScript field in client projects to load a file from an external domain while legitimate code continued to arrive from cdn.optimizely.com. The campaign began at 04:21 UTC on the BBC script and saw 26 payload updates throughout the day, including a card-data harvesting module added at 13:43 UTC. The malicious script could not access Stripe or Adyen payment forms inside iframes but attempted iOS exploit chains Coruna and DarkSword on affected devices. Optimizely confirmed the breach resulted from a vulnerability in Experimentation account registration, closed the flaw, removed the code and notified customers. Content Security Policy blocked the payload on only 24 of 256 tested sites, and attackers collected roughly $7,040 in cryptocurrency before cleanup completed around 21:52 UTC.

Habr•Supply Chain & Open Source

Rspamd 4.3.0 Released with Improved Phishing Detection, Attachment Scanning and Authentication Hardening

In mid-November 2026, developer Vsevolod Stakhov released Rspamd 4.3.0, the latest version of the open-source spam filtering system written in C, C++ and Lua under the Apache 2.0 license. The update strengthens HTTP connection handling, URL-based phishing checks, SPF/DKIM/ARC authentication validation and SMTPUTF8 address parsing while adding more robust attachment and HTML analysis. Key improvements include separate scoring for displayed versus actual link destinations, stricter rejection of weak DKIM keys and duplicate tags, and better archive filename handling to prevent executable hiding. The release also introduces the HTML_TINY_PIXEL_TRACKER rule to detect tracking beacons and fixes multiple bugs that could cause worker crashes or memory issues after free. Several changes may require configuration adjustments for existing users, particularly around symbol options and stricter authentication policies. Rspamd continues to support high-throughput Milter integration with Postfix and Sendmail while offering an extensive Lua API for custom processing logic.