Which versions of vitor-js are malicious?

The following npm versions of vitor-js are flagged malicious: 9.3.130, 9.3.133. Treat any of these as compromised.

How do I remediate vitor-js if I installed it?

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

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

Yes — vitor-js is associated with the GHSA-x8pc-c9x5-4hj2 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 vitor-js 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 vitor-js (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vitor-js across your stack and pipelines.

Malicious package

vitor-jsnpm

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

MAL-2025-192603

Immediate action

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

npm uninstall vitor-js

What this malware does

The package vitor-js 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 'vitor-js' @ 9.3.133 (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

2 flagged

9.3.1309.3.133

Indicators of compromise (SHA-256)

59962d3857dd8e503c596b43fbb33337d27bea7c1f53e69a305e690913599163

23bd6760c1b98479c10035033bae4ed585e80c762bf7fd4c79d45bdc990a852e

7de16b636ca267473cf52ae76f75d6714d25a360fa546f28148d2274aae70717

a0b842f58beec1e76ddcf6536d490482c67fc8fc140f46e5fe12ba78b2c04e9f

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

Campaign

GHSA-x8pc-c9x5-4hj2

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks vitor-js-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