Which versions of reactlogo-load are malicious?

The following npm versions of reactlogo-load are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate reactlogo-load if I installed it?

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

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

Yes — reactlogo-load is associated with the IN-MAL-2026-019836 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 reactlogo-load across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for reactlogo-load (version 1.0.0).

Malicious package

reactlogo-loadnpm

Advisory published Sep 9, 2026Updated Sep 9, 2026

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

Malicious code in reactlogo-load (npm)

MAL-2026-16069

Immediate action

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

npm uninstall reactlogo-load

What this malware does

The package presents itself as a logo/color utility but its exported loadLogo() function extracts a URL from LSB-encoded bits of a PNG, fetches the response body, and executes it via a reflective Function-constructor invocation. The 'constructor' property name and the Function reference are hidden behind a deterministic string-shuffle helper (hsvMean) named as a color utility, so no plaintext 'constructor', 'Function', 'eval', or destination URL appears in the source. runInContext binds global.require, module, and exports into the executed script, giving the fetched code full Node runtime capability on the caller's host. Following the README's documented usage (vite/tailwind build integration) triggers the fetch-and-execute path, so arbitrary attacker-controlled code runs on any machine that adopts this library.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a0f9d76fcf9f229c0a11508004a2be764133c6195530c4d56563eb28c358ab5f

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-019836

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks reactlogo-load-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