Version 2.10.1 of @cap-js/db-service was compromised (remote access trojan dropper); other versions are not flagged as malicious. CyberXYZ Proxy blocks the affected versions. It also has 1 known vulnerability, the worst rated CRITICAL.
Supply chain compromise of legitimate SAP packages published by threat actor "cloudmtabot@gmail.com" impersonating SAP toolchain maintainers. All four compromised packages share the same fingerprint: setup.mjs (4.4 KB) and execution.js (11.1 MB) bundled in the tarball, with a preinstall hook of "node setup.mjs". Notably, setup.mjs is explicitly excluded from the package.json 'files' allowlist yet is still shipped in the tarball — a manifest evasion technique intended to hide the malicious file from allowlist inspection while still executing it on install. execution.js (11.1 MB) is anomalously large for these packages and is consistent with an embedded payload or exfiltration binary. Packages were published 2026-04-29T09:55Z.
@cap-js/db-service is the core database service layer for SAP CAP applications. It is a transitive dependency of most CAP projects, giving this compromise broad reach across SAP CAP deployments.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Reported by GitHub Advisory Database via OSV.
mitre ttp
T1195.001
// versions and what to do
Malicious
2.10.1
Move to
2.11.3 newest 2.x release, no known advisory
3.2.0 current release, no known advisory
If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.
// questionsIs @cap-js/db-service safe to install?
Version 2.10.1 of @cap-js/db-service was compromised (remote access trojan dropper). Other versions are not flagged as malicious.
Does @cap-js/db-service have known vulnerabilities?
Yes. CyberXYZ records 1 known vulnerability for @cap-js/db-service (npm), the worst rated CRITICAL. They are GHSA-pvw4-cvr4-97p8.
Which version of @cap-js/db-service should I use?
Use 2.11.3 or a later release that is not named as malicious. Versions named on this report as malicious must not be installed.
How do I check @cap-js/db-service before installing?
Search @cap-js/db-service in CyberXYZ Check at https://cyberxyz.io/check?q=%40cap-js%2Fdb-service. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 04:35 UTC. The most recent advisory here was published 2026-05-20. Updated continuously from NVD, GHSA, OSV and CNA feeds.