Malicious code in bpm-foundation-storage (npm)
Historical advisory saved 24 Oct 2026 13:17:17 UTC. The publisher may have updated it since then. Latest advisory.
osv · MAL-2026-13119
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (9e1e2729c7a957ee4366b693a24d178137743df7bf2ee5d65d3cecf3c8cfdc5f) On require, index.js loads _ext.js, which selects a platform-specific path, fetches an executable over HTTPS from string-concatenation-obfuscated hosts on the *.workers.dev and *.dl.wel1.ru namespaces (with a DNS TXT-record fallback that base64-decodes concatenated chunks into a binary), writes it to a temp directory under a masquerading name such as dotnet_diag_<hex>.exe on Windows or.cache_<hex> on POSIX, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. There is no hash or signature verification, destinations are reconstructed at runtime from split substring arrays, and a secondary DNS-over-TXT loader provides resilience against domain blocking. Any consumer that require()s bpm-foundation-storage triggers execution of attacker-controlled code on the installer's host. The package's declared purpose is a storage library; none of the observed behavior is consistent with that purpose.
- Source published
- 5 Aug 2026 14:21:36 UTC
- Source modified
- 5 Aug 2026 15:52:32 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.