MalwarePublished 1 Jun 2026Updated 14 Jul 2026

@emcd-vue/loans (npm) · Malicious Code

Affects @emcd-vue/loansSource GCVE Database

Malicious package : remove @emcd-vue/loans and rotate any secrets on hosts that installed it.

Data as of 14 Jul 2026, 09:27 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-5165

What to do

Remove @emcd-vue/loans from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@emcd-vue/loans	Affected 7.1.7 – 7.2.0 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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 (`emcd-vue@proton.me`). 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. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7b5f346a554fe9f5f7cfc733c36d4c92c373aea12e245ef70e1031f41ff76f05) On `npm install`, the declared postinstall script `scripts/postinstall.js` executes a heavily obfuscated (obfuscator.io-style) bundle that collects host identifiers (hostname, username, homedir), the full `process.env` (with Windows-specific keys such as USERDOMAIN, COMPUTERNAME, APPDATA, LOCALAPPDATA, TEMP, PROGRAMDATA), the tail of shell history, and the contents of a hardcoded list of files under the user's home directory that the package itself never created. The collected object is transmitted to a remote endpoint over HTTP(S) and additionally over a covert DNS channel: the payload is base32-encoded into subdomain labels and issued as `dns.Resolver().resolveTxt(...)` queries in chunks, bypassing HTTP egress filters. Endpoint hostnames, header names, and API strings are reconstructed at runtime via a shuffled string array with RC4/XOR decoders. Before exfiltrating, the script checks `process.argv` and `NODE_OPTIONS` for debugger indicators and performs a timing check to detect sandboxes, skipping the exfil if analysis instrumentation is detected. The package also exhibits dependency-confusion shape: metadata references an internal-looking scope and registry (`@emcd-vue`, `npm.emcd-vue.io`, `github.emcd-vue.io`) while being published to the public npm registry, and `dist/index.js` re-exports a `../src/index.js` that is absent from the tarball, so the package has no functional library surface — the postinstall is its only executable code. ## Source: ghsa-malware (21b6c74231987d412324ad5320918c42d954a7921042a39b549415cd799b6ad6) 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.

Impact

This malicious package compromises the security and privacy of the host by collecting extensive environment and user data, including potentially sensitive files, and exfiltrating it to an attacker-controlled server. The execution of a persistent second-stage payload increases the risk of ongoing unauthorized access or further malicious activity. The use of covert DNS channels and sandbox evasion techniques complicates detection and mitigation.

Defensive guidance

Users and organizations should avoid installing the @emcd-vue/loans package versions 7.1.7, 7.1.8, 7.1.9, and 7.2.0. Review and remove any installations of this package and related @emcd-vue scoped packages. Monitor for suspicious processes such as ~/.emcd-vue_init.js execution. Employ network controls to block connections to the indicated malicious domains (oob.moika.tech). Since this is a supply-chain attack, validate package provenance and consider using package allowlists or verified publishers.

Summary

The @emcd-vue/loans npm package, published under the @emcd-vue scope, is malicious software involved in a multi-package supply-chain attack. Upon installation, its postinstall script executes obfuscated code that collects host identifiers, environment variables, shell history, and certain user files. It then exfiltrates this data to a remote server using both HTTP(S) and covert DNS TXT queries to bypass network filters. The package downloads a platform-specific second-stage payload, writes it to a hidden file in the user's home directory, and executes it as a detached process that persists beyond npm's execution. The package uses dependency confusion tactics by referencing internal-looking scopes and registries but is published publicly. It also performs sandbox and debugger detection to evade analysis. The package versions 7.1.7, 7.1.8, 7.1.9, and 7.2.0 are affected.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2026, 10:14 UTC

Technical details

References

Community reviews