Which versions of @emcd-vue/loans are malicious?

The following npm versions of @emcd-vue/loans are flagged malicious: 7.1.8. Treat any of these as compromised.

How do I remediate @emcd-vue/loans if I installed it?

@emcd-vue/loans is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @emcd-vue/loans — how do I know if it already compromised me?

If @emcd-vue/loans 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 @emcd-vue/loans part of a known attack campaign?

Yes — @emcd-vue/loans is associated with the IN-MAL-2026-005832, IN-MAL-2026-005831 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 @emcd-vue/loans 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 @emcd-vue/loans (version 7.1.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @emcd-vue/loans across your stack and pipelines.

Malicious package

@emcd-vue/loansnpm

Malicious code in @emcd-vue/loans (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5165

Immediate action

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

npm uninstall @emcd-vue/loans

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. This package was published 90 seconds after sibling package @emcd-vue/auth on 2026-06-01 by the same anonymous account ([email protected]).

Confirmed to use identical infrastructure and dropper logic as @emcd-vue/auth: downloads a platform-specific second-stage payload from https://oob.moika.tech/payload/{platform} using X-Secret: l95HdDaz3kQx1Zsg3WxH6HvKANf51RY1, writes it to ~/.emcd-vue_init.js (dot-prefixed hidden file), and executes it as a detached, unref'd process that persists after npm exits. Beacons installation metadata to https://oob.moika.tech/report on completion.

The package ships a heavily obfuscated postinstall script (scripts/postinstall.js) that executes automatically on npm install. The file uses hex-mangled identifier names (_0x2556a0, _0x3929dc, _0x2f9082, etc.) consistent with string-array obfuscators commonly used to hide network exfiltration, credential harvesting, or remote payload execution. Obfuscation in a lifecycle hook is not a legitimate engineering practice — install-time scripts in legitimate packages are readable shell or plain JS. The package name (@emcd-vue/loans) advertises a Vue.js loans component, which has no plausible reason to require obfuscated postinstall logic. Installing this package will run the obfuscated code automatically with the privileges of the developer or build system performing npm install.

Malicious versions

1 flagged

7.1.8

Indicators of compromise (SHA-256)

5533f10b35ebd7228376d5d97b22009e7d836f198069a2ed894f0cc709fb2d44

febfe36bf4efb63283bdcac20e625459b8f63358c2e32921a747f29bb2d65917

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @emcd-vue/loans (version 7.1.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @emcd-vue/loans across your stack and pipelines.
If you installed it — respond
@emcd-vue/loans is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @emcd-vue/loans 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 @emcd-vue/loans 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/loans on npm has been identified as a malicious package (version 7.1.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005832IN-MAL-2026-005831

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @emcd-vue/loans-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring