Which versions of xpack-video-submission are malicious?

The following npm versions of xpack-video-submission are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.0.10. Treat any of these as compromised.

How do I remediate xpack-video-submission if I installed it?

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

If xpack-video-submission 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 xpack-video-submission part of a known attack campaign?

Yes — xpack-video-submission is associated with the GHSA-3mrc-3vpq-5qc6, RLMA-2026-01661, RLUA-2026-01839 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 xpack-video-submission 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 xpack-video-submission (11 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xpack-video-submission across your stack and pipelines.

Malicious package

xpack-video-submissionnpm

Malicious code in xpack-video-submission (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1163

Immediate action

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

npm uninstall xpack-video-submission

What this malware does

The package xpack-video-submission 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.

Malicious versions

11 flagged

1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.91.0.10

Indicators of compromise (SHA-256)

cd1903bd7a6c918e7a55bf9666fe2aec106c49cd0fbff801aa61d3cadfa8db6c

7775173f0b8d7a6612c5a88940a5e371896db6f065c1b7c94bf87b2fcb6f51a1

dff73dc924046a2cf6ca42cd701c17af380fd4246c2d22b189b1dc4a510624f4

61f61603ebbf91ae245159d4a762879dcde318debb84df28858ad539563d8d85

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 xpack-video-submission (11 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xpack-video-submission across your stack and pipelines.
If you installed it — respond
Remove xpack-video-submission 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 xpack-video-submission 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 xpack-video-submission 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. xpack-video-submission on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3mrc-3vpq-5qc6RLMA-2026-01661RLUA-2026-01839

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks xpack-video-submission-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