# MAL-2026-3178: Malicious code in @cap-js/sqlite (npm)


- **Type:** Malicious package
- **Package:** `@cap-js/sqlite` (npm)
- **Published:** 29 Apr 2026
- **Also known as:** GHSA-2h7r-x9v2-q52f

## What is MAL-2026-3178?

MAL-2026-3178 is a malicious package in @cap-js/sqlite, published on 29 Apr 2026. 

### Official description

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/sqlite is the SQLite adapter for SAP CAP applications, commonly used in local development and CI test environments where environment secrets and developer credentials are accessible.

The package @cap-js/sqlite was found to contain malicious code.

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.

## What should I do about MAL-2026-3178?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-3178 is a malicious package: @cap-js/sqlite (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-3178/ (Markdown: https://insights.sbomify.com/MAL-2026-3178/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-3178

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-3178/
Summaries are generated and may contain mistakes; the official description above is the record.