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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for reactlogo-load (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging reactlogo-load across your stack and pipelines.

Malicious package

reactlogo-loadnpm

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for reactlogo-load (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging reactlogo-load across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks reactlogo-load before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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