Which versions of bvm-core are malicious?

The following npm versions of bvm-core are flagged malicious: 1.1.42, 1.1.43. Treat any of these as compromised.

How do I remediate bvm-core if I installed it?

bvm-core establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed bvm-core — how do I know if it already compromised me?

If bvm-core 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 bvm-core part of a known attack campaign?

Yes — bvm-core is associated with the IN-MAL-2026-010781, IN-MAL-2026-010782 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 bvm-core across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bvm-core (2 malicious versions).

Malicious package

bvm-corenpm

Advisory published Jul 16, 2026Updated Jul 16, 2026

bvm-core is a confirmed malicious npm package (MAL-2026-10728) that opens a backdoor for remote access (malicious versions 1.1.42, 1.1.43). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bvm-core (npm)

MAL-2026-10728

Immediate action

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

npm uninstall bvm-core

What this malware does

dist/index.js in [email protected] imports child_process and issues fetch() calls to the hardcoded host https://bvm-core.nexsail.top at the top of the bundled module, alongside a secondary fetch to registry.npmmirror.com. The combination — a lookalike domain that mirrors the package name on an unrelated TLD, module-load-time network calls, and child_process usage in the same bundle — is the fingerprint of an install/import-time beacon and command execution channel, not a legitimate SDK call. The package name resembles established bvm version-manager tooling but the code routes traffic to an author-controlled host on nexsail.top rather than to any documented registry or vendor endpoint.

Malicious versions

2 flagged

1.1.421.1.43

Indicators of compromise (SHA-256)

87ff2c7d903c5594ba5fa2e11d3fe6281380a5f2d010a1a0e3c0679464ab1fca

f8ba5a35e4424e78202f6d7af907dd7e46b6381b81eba8bbabb126a2e02579c1

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for bvm-core (2 malicious versions).
If you installed it — respond
bvm-core establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If bvm-core 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. bvm-core on npm has been identified as a malicious package (versions 1.1.42, 1.1.43 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010781IN-MAL-2026-010782

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bvm-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database