Which versions of static-content-cannabis are malicious?

The following npm versions of static-content-cannabis are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate static-content-cannabis if I installed it?

Remove static-content-cannabis 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 static-content-cannabis — how do I know if it already compromised me?

If static-content-cannabis 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 static-content-cannabis part of a known attack campaign?

Yes — static-content-cannabis is associated with the RLMA-2026-01590 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 static-content-cannabis across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for static-content-cannabis (version 999.0.0).

Malicious package

static-content-cannabisnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

static-content-cannabis is a confirmed malicious npm package (MAL-2026-1856) that executes malicious code on install (malicious version 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in static-content-cannabis (npm)

MAL-2026-1856

Immediate action

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

npm uninstall static-content-cannabis

What this malware does

The package static-content-cannabis was found to contain malicious code.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

4fe93ac5ef5776e697bbe75fc2f2f6e2db689ed31cc6410fca807dd79b653e4f

ad874c892146b9bd12da1a27cfcf9bb790ac0fa7f7e82c795585e7343806eb1b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for static-content-cannabis (version 999.0.0).
If you installed it — respond
Remove static-content-cannabis 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 static-content-cannabis 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. static-content-cannabis on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01590

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks static-content-cannabis-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