Which versions of internal-secret-project-1234 are malicious?

The following npm versions of internal-secret-project-1234 are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate internal-secret-project-1234 if I installed it?

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

If internal-secret-project-1234 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 internal-secret-project-1234 part of a known attack campaign?

Yes — internal-secret-project-1234 is associated with the RLMA-2026-01359 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 internal-secret-project-1234 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for internal-secret-project-1234 (version 99.99.99).

Malicious package

internal-secret-project-1234npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

internal-secret-project-1234 is a confirmed malicious npm package (MAL-2026-1753) 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 internal-secret-project-1234 (npm)

MAL-2026-1753

Immediate action

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

npm uninstall internal-secret-project-1234

What this malware does

The package internal-secret-project-1234 was found to contain malicious code.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

73e12ef20565f23999fe7a0ad382aa51b00c5d0d82156c6b2f531561a01ff245

c8dc95d958f766e3d4594c0ea651f834cd877966e5c76347c4f0d819eb5e79d7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for internal-secret-project-1234 (version 99.99.99).
If you installed it — respond
Remove internal-secret-project-1234 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 internal-secret-project-1234 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. internal-secret-project-1234 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-01359

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks internal-secret-project-1234-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