Which versions of vds-monarch are malicious?

The following npm versions of vds-monarch are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate vds-monarch if I installed it?

Remove vds-monarch 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 vds-monarch — how do I know if it already compromised me?

If vds-monarch 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 vds-monarch part of a known attack campaign?

Yes — vds-monarch is associated with the GHSA-w2rp-7fhc-hmrm 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 vds-monarch 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 vds-monarch (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vds-monarch across your stack and pipelines.

Malicious package

vds-monarchnpm

Malicious code in vds-monarch (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-929

Immediate action

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

npm uninstall vds-monarch

What this malware does

The package vds-monarch was found to contain malicious code.

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 'vds-monarch' @ 1.0.3 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

2973ebe630a7a180fd966248f177b9285bbcd6922d110318ff27d36648db51c7

b9fc03a6a0feff43eef44ac91f0e9ce68c422a439528842f139bf1164366c66d

23d64f4764ccc88b26aa567b6d6828093fe8d35500ac67a19ced44828073dbf4

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 vds-monarch (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vds-monarch across your stack and pipelines.
If you installed it — respond
Remove vds-monarch 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 vds-monarch 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 vds-monarch 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. vds-monarch on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w2rp-7fhc-hmrm

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks vds-monarch-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