finance-business-company-id-modelsnpm
finance-business-company-id-models is a confirmed malicious npm package (MAL-2026-12382) that executes malicious code on install (malicious version 20.1.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in finance-business-company-id-models (npm)
What this malware does
On require() of this package, index.js loads _compat.js which reconstructs destination hostnames from string-split arrays (e.g. "oob-worker.cf102-baf.workers"+".d"+".ev") to fetch a platform-specific binary via https.get, with a DNS-TXT chunked fallback across tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The downloaded bytes are written to /var/tmp or %TEMP% under disguised names (.cache_<rand>, dotnet_diag_<rand>.exe, .analytics_state), chmod'd 0755, and spawned detached via cp.spawn("/bin/sh", ["-c", fp+" &"], {detached:true}) on POSIX or cmd.exe /c start /b on Windows, with no hash or signature verification. lib/telemetry.js contains a second dropper of the same shape, loading child_process via require("child_"+"process") string-split, assembling a base64-chunk buffer, and chmod+exec'ing an "extension" path. The package's stated purpose is a "company id models" library; the network destinations, obfuscation, cover-story filenames, and platform-gated execution are unrelated to that purpose and match a supply-chain dropper campaign.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for finance-business-company-id-models (version 20.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging finance-business-company-id-models across your stack and pipelines.
If you installed it — respond
Remove finance-business-company-id-models from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If finance-business-company-id-models 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 finance-business-company-id-models 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 finance-business-company-id-models-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.