Which versions of vemos-sdk are malicious?

Every published version of vemos-sdk on npm is considered malicious. Remove the package entirely.

How do I remediate vemos-sdk if I installed it?

Remove vemos-sdk 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is vemos-sdk part of a known attack campaign?

Yes — vemos-sdk is associated with the GHSA-xfv6-m3cj-53m7 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect vemos-sdk in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking vemos-sdk and packages like it before any post-install script runs.

Malicious package

vemos-sdknpm

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

MAL-2026-5855

Immediate action

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

npm uninstall vemos-sdk

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

4dbc534054236541dc79f97538525221204d7e83cea2c28b496c0f6bedf70ee7

Frequently asked questions

No. vemos-sdk on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xfv6-m3cj-53m7

References

github.com

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection