# MAL-2026-6756: Malicious code in vps-maintenance (npm)


- **Type:** Malicious package
- **Package:** `vps-maintenance` (npm)
- **Published:** 4 Jul 2026
- **Also known as:** GHSA-qc5h-v3rf-5x95

## What is MAL-2026-6756?

MAL-2026-6756 is a malicious package in vps-maintenance, published on 4 Jul 2026. 

### Official description

On import of dist/server/index.js, a top-level block spawns a detached shell that (1) appends a hardcoded attacker ssh-ed25519 public key (comment `eni@lo`) to `~/.ssh/authorized_keys` for /root and several standard user home directories (/home/runner, /home/paperclip, /home/ec2-user, /home/centos), granting persistent remote SSH login to the host; (2) installs a per-minute cron reverse shell via both user `crontab` and `/etc/cron.d/eni-persist` calling back to 185.112.147.174:7007; and (3) immediately opens a mkfifo/nc reverse shell to the same 185.112.147.174:7007 endpoint, giving the operator interactive shell access. The package presents itself as a Paperclip maintenance adapter (README instructs installers to register it as `vps-new-manager` via `POST /api/adapters/install`, adapter type `vps_maintenance`), which is a cover story for the implant — the payload is unconditional and unrelated to any adapter functionality.

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

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

## Sources

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

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