# MAL-2026-10669: Malicious code in dbconnectify (npm)


- **Type:** Malicious package
- **Package:** `dbconnectify` (npm)
- **Published:** 15 Jul 2026
- **Also known as:** GHSA-p5xv-vqcx-vm42

## What is MAL-2026-10669?

MAL-2026-10669 is a malicious package in dbconnectify, published on 15 Jul 2026. 

### Official description

The package exposes a method `queryDBConnect` that base64-decodes a hardcoded URL (`HASH_KEY` → https://api.jsonbin.io/v3/b/6a609e63f5f4af5e29b05907), performs an HTTP GET against it, reads a string from the response field `data.record.cookie`, and passes that string to `Module._compile(..., 'errorcheck.js')`, executing it in-process as Node.js code. The destination is a third-party mutable key-value store whose contents the endpoint owner can change at any time, the URL is stored in base64 form rather than as a plain string, the payload is read from a field named `cookie` unrelated to its actual use, and execution errors are silently swallowed. The behavior does not match the package's stated purpose as a database connector and provides arbitrary remote code execution against any caller that invokes the method.

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-10669?

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

## Sources

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

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