Which versions of whaleco-assets-json are malicious?

The following npm versions of whaleco-assets-json are flagged malicious: 99.9.9, 100.0.5. Treat any of these as compromised.

How do I remediate whaleco-assets-json if I installed it?

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

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

Yes — whaleco-assets-json is associated with the RLMA-2026-05364, RLUA-2026-06549 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 whaleco-assets-json across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for whaleco-assets-json (2 malicious versions).

Malicious package

whaleco-assets-jsonnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

whaleco-assets-json is a confirmed malicious npm package (MAL-2026-7438) that executes malicious code on install (malicious versions 99.9.9, 100.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in whaleco-assets-json (npm)

MAL-2026-7438

Immediate action

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

npm uninstall whaleco-assets-json

Malicious versions

2 flagged

99.9.9100.0.5

Indicators of compromise (SHA-256)

db4256d083d055187fbaca989dd04cc1e37620911d7a8c12c658e811790ebf43

ebabdc90229ba6c550eb237e1026eb66a7ddf65e0c424d3d10065e1d2a4301fb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05364RLUA-2026-06549

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks whaleco-assets-json-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