Which versions of storage-types are malicious?

The following npm versions of storage-types are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate storage-types if I installed it?

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

If storage-types was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is storage-types part of a known attack campaign?

Yes — storage-types is associated with the GHSA-f8wv-3jjp-qw4w, RLMA-2026-01594 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 storage-types across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for storage-types (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging storage-types across your stack and pipelines.

Malicious package

storage-typesnpm

Malicious code in storage-types (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-430

Immediate action

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

npm uninstall storage-types

What this malware does

The package storage-types was found to contain malicious code.

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.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

43db13077851634493e5c8eded5eb06487ff41dcb7dad90ab9a2e3101e14b323

d2793f12e0ee779bcb14e4a4a5198059f576c8f832a64238e1584d6b2cd34209

175b38ad34d4c4c0ae35af72383c62f733d6cc3a49feae64f5e8e3a09ed27892

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for storage-types (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging storage-types across your stack and pipelines.
If you installed it — respond
Remove storage-types 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 storage-types was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks storage-types before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

GHSA-f8wv-3jjp-qw4wRLMA-2026-01594

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks storage-types-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