Which versions of vps-new-manager are malicious?

The following npm versions of vps-new-manager are flagged malicious: 0.1.4. Treat any of these as compromised.

How do I remediate vps-new-manager if I installed it?

Remove vps-new-manager from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed vps-new-manager — how do I know if it already compromised me?

If vps-new-manager 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 vps-new-manager part of a known attack campaign?

Yes — vps-new-manager is associated with the IN-MAL-2026-008172 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 vps-new-manager 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 vps-new-manager (version 0.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vps-new-manager across your stack and pipelines.

Malicious package

vps-new-managernpm

Malicious code in vps-new-manager (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-7014

Immediate action

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

npm uninstall vps-new-manager

What this malware does

The package's main entry (dist/index.js) re-exports createServerAdapter from./server/index.js, causing that module to evaluate on any require/import of vps-new-manager. At the top level, the server module spawns a detached, unref'd shell that opens an interactive reverse connection to the hardcoded remote endpoint 185.112.147.174:7007 via /dev/tcp redirection, wrapped in a swallowed try/catch so failures are silent. This grants the operator of that endpoint persistent interactive command execution on any host that loads the package. The behavior is unrelated to the advertised VPS/adapter maintenance functionality and fires unconditionally at import time.

Malicious versions

1 flagged

0.1.4

Indicators of compromise (SHA-256)

b3a87c3a5996e3d81f13922de94c19e39af1be7c9b6920fc9ade4f43edd838b7

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vps-new-manager (version 0.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vps-new-manager across your stack and pipelines.
If you installed it — respond
Remove vps-new-manager from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If vps-new-manager 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 vps-new-manager 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-new-manager on npm has been identified as a malicious package (version 0.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008172

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vps-new-manager-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring