Which versions of @0l00000l/auth are malicious?

The following npm versions of @0l00000l/auth are flagged malicious: 1.1.3, 1.1.4. Treat any of these as compromised.

How do I remediate @0l00000l/auth if I installed it?

@0l00000l/auth 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 @0l00000l/auth — how do I know if it already compromised me?

If @0l00000l/auth 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 @0l00000l/auth part of a known attack campaign?

Yes — @0l00000l/auth is associated with the IN-MAL-2026-016379, IN-MAL-2026-016380 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 @0l00000l/auth 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 @0l00000l/auth (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @0l00000l/auth across your stack and pipelines.

Malicious package

@0l00000l/authnpm

@0l00000l/auth is a confirmed malicious npm package (MAL-2026-13407) that steals credentials and exfiltrates sensitive data (malicious versions 1.1.3, 1.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @0l00000l/auth (npm)

MAL-2026-13407

Immediate action

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

npm uninstall @0l00000l/auth

What this malware does

The package presents itself as a generic authentication library and exposes register/login/logout/verifyEmail/forgotPassword/resetPassword/verifyToken handlers plus an Express authMiddleware. Each handler POSTs the caller's req.body — including plaintext passwords, email addresses, and Authorization headers — to the hardcoded destination https://be-aauth-production.up.railway.app/api/v1/.... The destination is a string literal in the code with no environment-variable override, no configuration API, and no mention in the README. Any Express app that mounts these methods as route handlers will forward its own end users' credentials to this third-party Railway host on every authentication request. The package name uses digit/letter homoglyphs (@0l00000l/auth) consistent with impersonation of a legitimate auth library.

Malicious versions

2 flagged

1.1.31.1.4

Indicators of compromise (SHA-256)

cb367562977f8319b3d37aab67a64f2298ae3a9b41d5980a7c66d22c3d135923

eb2d5f2ba1c8d7398787d4fa499a83a714823d751a26191dccd467bceecfce2f

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 @0l00000l/auth (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @0l00000l/auth across your stack and pipelines.
If you installed it — respond
@0l00000l/auth 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 @0l00000l/auth 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 @0l00000l/auth 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. @0l00000l/auth on npm has been identified as a malicious package (versions 1.1.3, 1.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016379IN-MAL-2026-016380

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @0l00000l/auth-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