Which versions of rai6jaisahthaghee5ou-loader-package are malicious?

The following npm versions of rai6jaisahthaghee5ou-loader-package are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate rai6jaisahthaghee5ou-loader-package if I installed it?

rai6jaisahthaghee5ou-loader-package is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed rai6jaisahthaghee5ou-loader-package — how do I know if it already compromised me?

If rai6jaisahthaghee5ou-loader-package 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 rai6jaisahthaghee5ou-loader-package part of a known attack campaign?

Yes — rai6jaisahthaghee5ou-loader-package is associated with the IN-MAL-2026-020622 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 rai6jaisahthaghee5ou-loader-package 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 rai6jaisahthaghee5ou-loader-package (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 rai6jaisahthaghee5ou-loader-package across your stack and pipelines.

Malicious package

rai6jaisahthaghee5ou-loader-packagenpm

rai6jaisahthaghee5ou-loader-package is a confirmed malicious npm package (MAL-2026-17238) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rai6jaisahthaghee5ou-loader-package (npm)

MAL-2026-17238

Immediate action

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

npm uninstall rai6jaisahthaghee5ou-loader-package

What this malware does

The package's main module is an IIFE that injects a <script> element pointing at the hardcoded URL https://nee1ahnaw7.xsses.link and appends it to the document, causing whatever JavaScript that host serves to execute in the caller's page context. The destination is unpinned, opaque, unrelated to the package's declared identity or publisher, and the host name aligns with XSS/payload delivery infrastructure. Any application that bundles this dependency will fetch and execute attacker-controlled JavaScript at runtime, granting full code execution within the app's origin — enabling credential/session theft, arbitrary DOM manipulation, and further payload staging.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6de53fbd264f685e033789fe5929c63f322366219d80707ec419a48a85e253c9

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rai6jaisahthaghee5ou-loader-package (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 rai6jaisahthaghee5ou-loader-package across your stack and pipelines.
If you installed it — respond
rai6jaisahthaghee5ou-loader-package is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If rai6jaisahthaghee5ou-loader-package 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 rai6jaisahthaghee5ou-loader-package 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. rai6jaisahthaghee5ou-loader-package 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-020622

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks rai6jaisahthaghee5ou-loader-package-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database