Which versions of vapark-boost-v1 are malicious?

The following npm versions of vapark-boost-v1 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate vapark-boost-v1 if I installed it?

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

If vapark-boost-v1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is vapark-boost-v1 part of a known attack campaign?

Yes — vapark-boost-v1 is associated with the RLMA-2025-06521 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 vapark-boost-v1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for vapark-boost-v1 (version 1.0.1).

Malicious package

vapark-boost-v1npm

Advisory published Dec 23, 2025Updated Jan 2, 2026

vapark-boost-v1 is a confirmed malicious npm package (MAL-2025-192882) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vapark-boost-v1 (npm)

MAL-2025-192882

Immediate action

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

npm uninstall vapark-boost-v1

What this malware does

The package vapark-boost-v1 was found to contain malicious code.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

328bccbf5505ca7b557369f0f1ba3ce8ca542fa485b479ffca126a2119a046b9

673cefe658424d45a9a7d0435722d098c258180f931cf3a92f945128d8cb83e0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for vapark-boost-v1 (version 1.0.1).
If you installed it — respond
Remove vapark-boost-v1 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 vapark-boost-v1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. vapark-boost-v1 on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06521

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks vapark-boost-v1-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