Which versions of @vmo-community/video-player are malicious?

The following npm versions of @vmo-community/video-player are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate @vmo-community/video-player if I installed it?

Remove @vmo-community/video-player 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 @vmo-community/video-player — how do I know if it already compromised me?

If @vmo-community/video-player 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 @vmo-community/video-player part of a known attack campaign?

Yes — @vmo-community/video-player is associated with the RLMA-2026-04806, RLUA-2026-05941 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 @vmo-community/video-player across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @vmo-community/video-player (version 9.9.9).

Malicious package

@vmo-community/video-playernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@vmo-community/video-player is a confirmed malicious npm package (MAL-2026-7100) that executes malicious code on install (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @vmo-community/video-player (npm)

MAL-2026-7100

Immediate action

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

npm uninstall @vmo-community/video-player

Malicious versions

1 flagged

9.9.9

Indicators of compromise (SHA-256)

dee23481109118afa3fd5fd1cf42c8db774a37cddbf7fe52ab727e813dcc6443

64efc8a1a317532f86b5ce93db8bc8eef865a1223bf1a8c6689ff614f00f2745

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @vmo-community/video-player (version 9.9.9).
If you installed it — respond
Remove @vmo-community/video-player 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 @vmo-community/video-player 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. @vmo-community/video-player on npm has been identified as a malicious package (version 9.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04806RLUA-2026-05941

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @vmo-community/video-player-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