Which versions of @cap-js/postgres are malicious?

The following npm versions of @cap-js/postgres are flagged malicious: 2.2.2. Treat any of these as compromised.

How do I remediate @cap-js/postgres if I installed it?

@cap-js/postgres is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @cap-js/postgres — how do I know if it already compromised me?

If @cap-js/postgres was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @cap-js/postgres part of a known attack campaign?

Yes — @cap-js/postgres is associated with the GHSA-7vv3-r527-wvjr campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @cap-js/postgres across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @cap-js/postgres (version 2.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @cap-js/postgres across your stack and pipelines.

Malicious package

@cap-js/postgresnpm

Malicious code in @cap-js/postgres (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3177

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @cap-js/postgres

What this malware does

Supply chain compromise of legitimate SAP packages published by threat actor "[email protected]" 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/postgres is the PostgreSQL database adapter for SAP's Cloud Application Programming (CAP) model. Its presence in CI/CD pipelines gives the payload access to database credentials and build environment secrets.

The package @cap-js/postgres 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.

Malicious versions

1 flagged

2.2.2

Indicators of compromise (SHA-256)

d5d183f241500547c1956a14e7abd4ef842eaa0040900ccd3eff80b1ae046405

38808eb534a2ed04b732a3acb7e4f8bd0aae8c2d64123d611a6565d5ce9440dd

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @cap-js/postgres (version 2.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @cap-js/postgres across your stack and pipelines.
If you installed it — respond
@cap-js/postgres is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @cap-js/postgres was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @cap-js/postgres before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @cap-js/postgres on npm has been identified as a malicious package (version 2.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7vv3-r527-wvjr

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @cap-js/postgres-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring