Which versions of node-vite-config are malicious?

The following npm versions of node-vite-config are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate node-vite-config if I installed it?

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

If node-vite-config 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 node-vite-config part of a known attack campaign?

Yes — node-vite-config is associated with the GHSA-6rqx-6vc7-25fv, RLMA-2025-05092, RLUA-2025-05461, RLUA-2025-05896 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 node-vite-config 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 node-vite-config (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-vite-config across your stack and pipelines.

Malicious package

node-vite-confignpm

node-vite-config is a confirmed malicious npm package (MAL-2025-47489) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-vite-config (npm)

MAL-2025-47489

Immediate action

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

npm uninstall node-vite-config

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

c53bdee988880e8c288daeff8bb041022f69c78319375b597edab208129e0621

6a96b83988df61ca08ae3765204cfb15dd0aca671d243b031e6dd26d6ba790b7

e7d64b3808d17732754e9cd5ac9ac3fef754d0a0985836857ad32d55fef8b1d0

feff56d8cd39dfa3a75e8cc37fe650b42b1c336eb4892d91b45ff7db8e1ca0fe

2fff3586f41858f2e81b01f5495a971c76d301d751abef382c5ea0eae4d822f9

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

Campaign

GHSA-6rqx-6vc7-25fvRLMA-2025-05092RLUA-2025-05461RLUA-2025-05896

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks node-vite-config-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

Explore

All malware advisories How O3 detects malware Vulnerability database