Which versions of okta-loginpage-render are malicious?

Every published version of okta-loginpage-render on npm is considered malicious. Remove the package entirely.

How do I remediate okta-loginpage-render if I installed it?

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

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

Yes — okta-loginpage-render is associated with the GHSA-mpr5-992q-49cx 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 okta-loginpage-render across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for okta-loginpage-render (all published versions).

Malicious package

okta-loginpage-rendernpm

Advisory published Jan 6, 2026Updated Jan 8, 2026

okta-loginpage-render is a confirmed malicious npm package (MAL-2026-92) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in okta-loginpage-render (npm)

MAL-2026-92

Immediate action

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

npm uninstall okta-loginpage-render

What this malware does

The package okta-loginpage-render was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

9f8fb7a7fef0eac00d82269765ba3c3e56f23b334f8053108fe1728cacd97200

48116f31c0b827072f94f6157837d2fcb3be3c6a9985584328216403280bd6bb

Detection & response playbook

Malicious package

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

Campaign

GHSA-mpr5-992q-49cx

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks okta-loginpage-render-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