Malicious code in brass-common (npm)

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (657abbbfdd17b21af7ad85e8634e0fb2ac36e35c6b95996322f10584ef4c1570) [email protected] declares its only dependency `ltidisafe` as a direct HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.6.tgz) in package.json rather than a registry version range. `npm install` fetches and installs whatever bytes that URL currently returns, with no version pin, no integrity hash, and no registry review, and runs any lifecycle scripts inside that tarball on the installer's machine. The shipped index.js is a 35-byte stub exporting `{}`, so the manifest itself is the entire install-time payload. The implausibly high version number (99.9.1) is consistent with a dependency-confusion shape intended to win resolution against an internal package of the same name. ## Source: ghsa-malware (4ed6d4725f0bc042716325034a4d32837a91a2c003826c6b6c835aaf86cfc3f1) 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: ossf-package-analysis (ab25e940e6abf9009b89e6480c744db72c4ea0be4d83d095ead744e83055b7cf) The OpenSSF Package Analysis project identified 'brass-common' @ 99.9.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Source published

13 Oct 2026 07:45:45 UTC

Source modified

26 Oct 2026 01:45:20 UTC

Observed here

26 Oct 2026 02:35:24 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.