Which versions of brass-common are malicious?

The following npm versions of brass-common are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate brass-common if I installed it?

Remove brass-common 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.

I already installed brass-common — how do I know if it already compromised me?

If brass-common was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is brass-common part of a known attack campaign?

Yes — brass-common is associated with the IN-MAL-2026-021500 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find brass-common across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for brass-common (version 99.9.1).

Malicious package

brass-commonnpm

Advisory published Oct 13, 2026Updated Oct 16, 2026

brass-common is a confirmed malicious npm package (MAL-2026-17849) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in brass-common (npm)

MAL-2026-17849

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall brass-common

What this malware does

[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.

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.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

ab25e940e6abf9009b89e6480c744db72c4ea0be4d83d095ead744e83055b7cf

657abbbfdd17b21af7ad85e8634e0fb2ac36e35c6b95996322f10584ef4c1570

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for brass-common (version 99.9.1).
If you installed it — respond
Remove brass-common 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 brass-common was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. brass-common on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021500

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks brass-common-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database