Which versions of pkg1511222 are malicious?

The following npm versions of pkg1511222 are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate pkg1511222 if I installed it?

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

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

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

Search your lockfiles and build artifacts for pkg1511222 (version 99.99.99).

Malicious package

pkg1511222npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in pkg1511222 (npm)

MAL-2026-1815

Immediate action

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

npm uninstall pkg1511222

What this malware does

The package pkg1511222 was found to contain malicious code.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

55f0926870b4bb08a1cf69aa3cd7994c85b809ec8b025fcb409d4c6b2805258b

1b5668eede47a133fd2d8705650da92721b0d22cc494e9ed77e7adb8bf416813

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01491

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks pkg1511222-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