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

@car_loans/dealerships-approvalnpm

@car_loans/dealerships-approval is a confirmed malicious npm package (MAL-2026-10397) that steals credentials and exfiltrates sensitive data (malicious versions 7.1.5, 7.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @car_loans/dealerships-approval (npm)

MAL-2026-10397
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @car_loans/dealerships-approval

What this malware does

@car_loans/dealerships-approval 7.1.5 self-describes as a 'browserslist config' but ships a heavily obfuscated postinstall dropper. package.json declares "postinstall": "node scripts/postinstall.js"; that script uses a rotating string-array + RC4 decoder plus byte-array-to-String.fromCharCode wrappers to hide every module name, method, and URL fragment. On npm install, the script HTTPS-GETs a remote payload assembled from base64 fragments, RC4-decrypts the response, writes it to disk, chmods 0o755, and spawns it detached with stdio:'ignore' and unref() — attacker-controlled code executed on the installer's machine with no user interaction. Before and after payload execution, it collects os.hostname(), os.userInfo().username, platform, arch, package name/version, and an event tag and POSTs them to a base64-assembled remote host; it also encodes fingerprint data into <hex>.<rand>.<host> subdomain labels and calls dns.resolve4 as a DNS-tunnel side channel intended to bypass HTTP egress filtering. The package additionally exhibits the classic dependency-confusion shape: an unusual underscore scope @car_loans/*, README that labels it an 'Internal package — Platform Engineering Team', and homepage/repository/registry URLs on the non-existent car-loans.io domain instructing consumers to point .npmrc at https://npm.car-loans.io. Any developer at a targeted organization who resolves this name from the public registry receives immediate install-time code execution and host fingerprint exfiltration.

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

2 flagged
7.1.57.1.6

Indicators of compromise (SHA-256)

326f8f463729022112e04c36fd7a67e785ad8fc37f8e7eec19f60738597bd43d
3a5f2502fb53db978afaa82d37fde7e3dfb443d08fb5a570087aaa5374a9e562
37c0db1ff609f47e855c7cb44d4c8001f5595f8d2db278885c952a96b4b80a38

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    @car_loans/dealerships-approval 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.

  3. Did it already run?

    If @car_loans/dealerships-approval 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 @car_loans/dealerships-approval 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. @car_loans/dealerships-approval on npm has been identified as a malicious package (versions 7.1.5, 7.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009796GHSA-p8xg-5qpp-p289IN-MAL-2026-013019

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

@car_loans/dealerships-approval (npm) malicious package — MAL-2026-10397 | O3 Security