@loans/vehicles-apinpm
Malicious code in @loans/vehicles-api (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
@loans/vehicles-api is a dependency-confusion package targeting an internal @loans npm scope (claimed homepage docs.loans.io, README directs users to a private registry npm.loans.io) but published to the public npm registry with a malicious scripts/postinstall.js. On npm install, the postinstall script (1) downloads a per-OS payload from https://oob.moika.tech/payload/{linux,mac,win}, writes it to os.tmpdir() as._loans_init.sh/.bat, chmods 0755, and spawns it via /bin/sh or cmd.exe with no hash/signature verification — unconditional install-time remote code execution; (2) enumerates process.env for credential-shaped keys (npm_token, npm_config_authtoken, node_auth_token, npm_config__auth, github_token, aws_access_key_id, aws_secret_access_key, aws_session_token, artifactory_token, nexus_token) and POSTs the values to https://oob.moika.tech/report; (3) reads ~/.npmrc, /etc/npmrc,./.npmrc, and../.npmrc (which commonly contain registry _authToken entries) and exfiltrates their contents; (4) collects host fingerprint (hostname, username, platform, arch, cwd, node/npm versions, full PATH, CI flags) and self-identifies in the JSON payload as poc: 'dependency-confusion-npm'. The destination domain oob.moika.tech does not match the claimed publisher (loans.io). Any installer whose internal resolver selects this public version is fully compromised at install time.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @loans/vehicles-api (version 9.9.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @loans/vehicles-api across your stack and pipelines.
If you installed it — respond
@loans/vehicles-api 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 @loans/vehicles-api 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 @loans/vehicles-api 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @loans/vehicles-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.