Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

vps-adapter-corenpm

vps-adapter-core is a confirmed malicious npm package (MAL-2026-6949) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vps-adapter-core (npm)

MAL-2026-6949
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall vps-adapter-core

What this malware does

The package 'vps-adapter-core' is a purpose-built malware package published by the npm account 'srm0rgan' ([email protected]) as part of a coordinated campaign of fake 'Paperclip' VPS-maintenance adapters (siblings: paperclip2, vps-maintenance, vps-maintenance-paperclip-adapter, paperclip-host-utils). Every published version (1.0.0, 1.0.1, 1.0.2) declares a postinstall script (node postinstall.js) that npm runs automatically during npm install, while index.js is a benign stub (init()/status()) that serves only as cover.

The postinstall payload performs four malicious actions with best-effort error suppression:

  1. SSH backdoor: appends the attacker's ed25519 public key (comment eni@lo, AAAAC3NzaC1lZDI1NTE5AAAAIDGA+v9tfK8YVeZejZN2y99mNvefRmQx99lJtjKjIAK2) to ~/.ssh/authorized_keys, granting the operator persistent remote SSH access.

  2. Cron persistence: writes /etc/cron.d/eni-persist containing per-minute (* * * * * root) and @reboot entries that open bash reverse shells to 185.112.147.174 across ports 7007, 443, 80, 8080, 4444, 5555, 1337, and 9001 via /dev/tcp.

  3. Credential exfiltration: spawns a detached bash pipeline that dumps host identity, bash history, and a broad sweep of secrets — AWS/Azure/GCP/OCI credentials, kubeconfig, Docker config, git/pip/npm/netrc credentials, .env files, SSH private keys (id_rsa/id_ed25519/id_ecdsa/id_github/id_deploy_key), /etc/shadow, and /etc/passwd — plus a filesystem search for files matching 'maid' and for database files, then pipes the collected data to 185.112.147.174 over /dev/tcp across the same eight ports.

  4. Interactive reverse shells: spawns detached interactive bash reverse shells to the same host/ports.

A keepAlive() timer re-runs the credential dump and reverse-shell spawns every 30 seconds, and a cleanNpmStains() routine deletes npm cache traces of the sibling campaign packages to hinder detection. Any developer workstation or CI job that runs npm install vps-adapter-core must be considered fully compromised; all credentials and SSH keys reachable from that host should be rotated from a separate, clean machine, and /etc/cron.d/eni-persist and the attacker key in authorized_keys removed.

On npm install, the package's declared postinstall script (postinstall.js) executes an end-to-end host takeover against the installing user: (1) appends a hardcoded attacker ssh-ed25519 key ('eni@lo') to /.ssh/authorized_keys, granting persistent SSH access; (2) writes /etc/cron.d/eni-persist to re-open reverse bash shells to 185.112.147.174 every minute and at @reboot across ports 7007, 443, 80, 8080, 4444, 5555, 1337, 9001; (3) immediately spawns interactive bash -i reverse shells to the same IP/ports via /dev/tcp and keeps them alive with a 30-second setInterval; (4) reads and exfiltrates classic installer secrets and root-only files (/.aws/credentials, ~/.ssh/id_*, ~/.kube/config, ~/.docker/config.json, ~/.npmrc, ~/.git-credentials, ~/.netrc, /etc/shadow, /etc/passwd, shell history) over raw TCP to the same attacker IP; (5) removes sibling directories under ~/.paperclip/adapter-plugins/node_modules matching related adapter/helper names, consistent with removing competing implants from the same campaign. Any developer or CI system that installs this package is fully compromised at install time.

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.

The OpenSSF Package Analysis project identified 'vps-adapter-core' @ 1.0.2 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged
1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

9d8b04479e04cd28084836c7eb146dae23c03b7b318a98e415adce6433acadf3
721f18c9af5bbc2ee66386230d6d7c389cf862f4e5982c65a6368117a05b2f93
956346e6d654bb967254d1711a332bc337f50e2ad680b8f93e6fbae5f5e37e07
e58bf17e8d6fb4601047569ae61680ea38a380ecee5cfd68408ba22bf0dfb516
30e5ecc5aff58afdc90139a153ca99fa5266a698f7af82695f7235d1e9b919da

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vps-adapter-core (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vps-adapter-core across your stack and pipelines.

  2. If you installed it — respond

    vps-adapter-core 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.

  3. Did it already run?

    If vps-adapter-core 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.

  4. How O3 protects you

    O3 blocks vps-adapter-core 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. vps-adapter-core on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hvxm-858v-vhw9IN-MAL-2026-008042IN-MAL-2026-008043IN-MAL-2026-008045

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder
  • SafeDep · finder

Detect & block this

O3 blocks vps-adapter-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

vps-adapter-core (npm) malicious package — MAL-2026-6949 | O3 Security