Which versions of initial-path32 are malicious?

The following npm versions of initial-path32 are flagged malicious: 3.3.9. Treat any of these as compromised.

How do I remediate initial-path32 if I installed it?

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

If initial-path32 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 initial-path32 part of a known attack campaign?

Yes — initial-path32 is associated with the RLMA-2026-01355 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 initial-path32 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for initial-path32 (version 3.3.9).

Malicious package

initial-path32npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

initial-path32 is a confirmed malicious npm package (MAL-2026-1749) that executes malicious code on install (malicious version 3.3.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in initial-path32 (npm)

MAL-2026-1749

Immediate action

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

npm uninstall initial-path32

What this malware does

The package initial-path32 was found to contain malicious code.

Malicious versions

1 flagged

3.3.9

Indicators of compromise (SHA-256)

927ef536faffb8ea69bfa6e734182fc5b1e4ba1230271e6b1f6b8d124d291de9

71e77f0ff5d620fe6b79ce6c0ba799edb94b5ec3b8eea98b7da903d2f70e9c86

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01355

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks initial-path32-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