ZDF
Sign inSign up

Vulnerabilities

Vulnerability · MAL-2026-17849

Malicious code in brass-common (npm)

Published Oct 13, 2026 · catalog updated Oct 16, 2026 · Malicious code in brass-common

Open the advisory

Exploitation likelihood is not on this record for MAL-2026-17849. A missing EPSS score is not a low risk. Compare Malicious code in brass-common with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Malicious code in brass-common).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Not established
Affected products
npm brass-common

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (657abbbfdd17b21af7ad85e8634e0fb2ac36e35c6b95996322f10584ef4c1570) brass-common@99.9.1 declares its only dependency 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. 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: 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm brass-common99.9.1

How to fix MAL-2026-17849

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for MAL-2026-17849. A missing EPSS score is not a low risk. Compare Malicious code in brass-common with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 99.9.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 13, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (657abbbfdd17b21af7ad85e8634e0fb2ac36e35c6b95996322f10584ef4c1570) brass-common@99.9.1 declares its only dependency 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. fetches and installs whatever bytes that UR

  2. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (657abbbfdd17b21af7ad85e8634e0fb2ac36e35c6b95996322f10584ef4c1570) brass-common@99.9.1 declares its only dependency 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. fetches and installs whatever bytes that UR

Sources

References

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.