Which versions of vitest-environment-jsdom-patched are malicious?

The following npm versions of vitest-environment-jsdom-patched are flagged malicious: 5.0.0. Treat any of these as compromised.

How do I remediate vitest-environment-jsdom-patched if I installed it?

Remove vitest-environment-jsdom-patched 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 vitest-environment-jsdom-patched — how do I know if it already compromised me?

If vitest-environment-jsdom-patched 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 vitest-environment-jsdom-patched part of a known attack campaign?

Yes — vitest-environment-jsdom-patched is associated with the GHSA-g639-r35h-h4pw 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 vitest-environment-jsdom-patched 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 vitest-environment-jsdom-patched (version 5.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vitest-environment-jsdom-patched across your stack and pipelines.

Malicious package

vitest-environment-jsdom-patchednpm

Malicious code in vitest-environment-jsdom-patched (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191486

Immediate action

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

npm uninstall vitest-environment-jsdom-patched

What this malware does

The package vitest-environment-jsdom-patched 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 'vitest-environment-jsdom-patched' @ 5.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

5.0.0

Indicators of compromise (SHA-256)

d2b0241aa260a1945f1daedc5d2c085594a35a37bf98b20d1af4d39ddf6e13b4

4e0d8ae07807d73026bd13988c3341aecf8375b53ae436d03f80110884c5d84e

f482ff8bb13cef753c880dcd7f15cf48369c10056fc2ba5ee7b05e4feecc49ff

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

Campaign

GHSA-g639-r35h-h4pw

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks vitest-environment-jsdom-patched-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