Malicious code in api-nebula (npm)
Exact source revision recorded 24 Oct 2026 13:17:17 UTC. It does not establish the source's current position. Latest evidence.
osv · MAL-2026-17531
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b8232ec7756422686c2bce805fc87821e61a5bd9176cdb2fe7c3190fd2b2eae2) The package declares `"preinstall": "node preinstall.cjs"` in package.json, and preinstall.cjs is a single-line ~187 KB `Function("pbeIUC", "…")` invocation implementing a custom PRNG plus string-table decoder (numeric constant table, printable-charset string table `UclPgF`, a Bob-Jenkins-style mixer, and a decoder that reconstructs strings via modular arithmetic against `UclPgF.charCodeAt(...)`). The file contains no readable logic — its entire payload is an opaque blob that is decoded and handed to the JS engine during `npm install`. String fragments visible pre-decoding (e.g. `F.kI`, `[email protected]`, `vCpP.BB/.i+gUAKa`) are placeholder-shaped and only resolve to real hosts/commands after runtime decoding, so the actual install-time behavior and any network destinations are hidden from static inspection. The wrapper module (nebula.js) and package.json declare no native build step, no compilation, and no other legitimate reason for a 187 KB obfuscated preinstall script. This is the canonical obfuscated npm preinstall dropper shape: arbitrary attacker-authored code executes on every installer's machine at `npm install` time, with intent to evade review deliberately concealed by the string-table + Function-eval loader. ## Source: ghsa-malware (630739715b86da1f9f4a6d39d1108dce9965678236516ee34c21ce5ab6f6def5) 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.
- Source published
- 5 Oct 2026 03:12:06 UTC
- Source modified
- 12 Oct 2026 15:45:05 UTC
- Observed 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
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.