Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@emcd-vue/b2b-pay-formnpm

@emcd-vue/b2b-pay-form is a confirmed malicious npm package (MAL-2026-5164) that opens a backdoor for remote access (malicious versions 5.7.3, 5.7.4, 5.7.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @emcd-vue/b2b-pay-form (npm)

MAL-2026-5164
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @emcd-vue/b2b-pay-form

What this malware does

Part of a coordinated multi-package supply-chain attack impersonating EMCD (emcd.io), a legitimate Russian cryptocurrency exchange and mining pool. The attacker registered the @emcd-vue npm scope to distribute multiple malicious packages posing as internal tooling under the "EMCD Platform Engineering" identity. This package was published on the same day as confirmed campaign packages @emcd-vue/auth and @emcd-vue/loans, which share C2 infrastructure at oob.moika.tech.

The package description ("Internal HTTP client with retry, auth injection and request tracing") is fabricated; the @emcd-vue scope has no affiliation with the real EMCD exchange (emcd.io). Campaign packages in this scope use a multi-stage postinstall dropper that downloads and executes a platform-specific payload from https://oob.moika.tech/payload/{platform} using a shared secret key, writes the payload to a hidden dot-file in the user's home directory, and beacons installation metadata to https://oob.moika.tech/report.

@emcd-vue/b2b-pay-form ships an obfuscator.io-encoded scripts/postinstall.js wired as the npm postinstall lifecycle hook. On npm install, the script builds a platform-keyed URL from os.platform(), performs an HTTPS GET of a remote payload, writes it to os.tmpdir(), and spawns it via spawn(process.execPath, [tmpFile], {detached:true}).unref() — a classic install-time dropper that grants the publisher arbitrary remote code execution on every installing host. An environment-variable kill switch and a TTL-gated JSON cache in the user home directory throttle re-execution to evade detection. The package's stated purpose is an 'Internal HTTP client'; fetching and executing remote Node code is unrelated to that purpose. The package metadata is also fabricated dependency-confusion bait: scope @emcd-vue and all referenced domains (emcd-vue.io, github.emcd-vue.io, jira.emcd-vue.io, docs.emcd-vue.io, npm.emcd-vue.io, telemetry.emcd-vue.io) are not owned by any public organization, and the README instructs consumers to point npm at https://npm.emcd-vue.io while branding the package as 'Internal package — Platform Engineering Team' — the canonical pattern for targeting orgs whose private internal scope matches @emcd-vue or whose CI lazily resolves unknown scopes from the public registry. The postinstall file itself is heavily obfuscated (string-array + RC4-style decoder, control-flow flattening, self-defending function, 109-entry encoded string table), which has no legitimate purpose for a lifecycle script and is consistent with evasion of review.

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

4 flagged
5.7.35.7.45.7.55.8.0

Indicators of compromise (SHA-256)

a7ba596c8dca7145a8e505cdb4cf2c96dd1a4e741ea55192e076da181ecc6d38
e45e677cee670117b0ff7dcdf2f04491cfb61385025a178e197ea35924e9410e
e79de3341867d04d08fa606ab88a0a0d306adaf2b1e1aac3d5301c8ef2590d23
fb2341faa5bb4d4b363651831ecb13f4bb45eaa27a3a5ef6f7ca48a7f4bf0de2
2fc49e259169a9cbb0a1412a88cf70f42f05d15dbda4bf60027d5425e3efc679
d90cd206861b8a82dbbf2519456e475cb2aae36d33267bfb0b6a512cf51366e4

Detection & response playbook

Backdoor / remote access
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @emcd-vue/b2b-pay-form (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @emcd-vue/b2b-pay-form across your stack and pipelines.

  2. If you installed it — respond

    @emcd-vue/b2b-pay-form 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.

  3. Did it already run?

    If @emcd-vue/b2b-pay-form 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.

  4. How O3 protects you

    O3 blocks @emcd-vue/b2b-pay-form 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. @emcd-vue/b2b-pay-form on npm has been identified as a malicious package (versions 5.7.3, 5.7.4, 5.7.5, 5.8.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006150IN-MAL-2026-006149IN-MAL-2026-008470IN-MAL-2026-008381IN-MAL-2026-009249GHSA-xqjh-fp6w-54g6

References

Credits

  • Amazon Inspector · finder
  • SafeDep · finder

Detect & block this

O3 blocks @emcd-vue/b2b-pay-form-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore