Which versions of auth0-open-source-template are malicious?

The following PyPI versions of auth0-open-source-template are flagged malicious: 20.1.0. Treat any of these as compromised.

How do I remediate auth0-open-source-template if I installed it?

auth0-open-source-template 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 auth0-open-source-template — how do I know if it already compromised me?

If auth0-open-source-template 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 auth0-open-source-template part of a known attack campaign?

Yes — auth0-open-source-template is associated with the RLMA-2025-00439, 2024-12- sajansubedi, RLUA-2026-00120 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 auth0-open-source-template 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 auth0-open-source-template (version 20.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging auth0-open-source-template across your stack and pipelines.

Malicious package

auth0-open-source-templatePyPI

Malicious code in auth0-open-source-template (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-901

Immediate action

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

pip uninstall auth0-open-source-template

What this malware does

The package looks like a beginning for a further work. In fact, the uploader has shortly published a few similar packages appearing to be e.g. an integration for a known application, but containing only a "telemetry" module exfiltrating basic info about the user. This package has no other purpose than collecting data about users. In addition, it appears to be largely generated by an LLM.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-12- sajansubedi

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
dependency-confusion

Malicious versions

1 flagged

20.1.0

Indicators of compromise (SHA-256)

6aa2b66e9ebc1c39d1c856b4b52062d76735f5c1167dbec4081d636e73d127bf

47433968af90982f1a3a1d327cdb07499f61db145f6fc3e76e360b90008b01c8

c14dd94f3cdea34f9073f26be0716cfd944e0362396ae1dccab12196021a328c

55de7f347b636eb3f765990bd93bc493710ebf76ab2b3a2a02ec814c22bdf848

4aeedbf9eb62096eaf83f53c299abcb8024d4e71fac224eddfc308b5f63d2f6b

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 auth0-open-source-template (version 20.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging auth0-open-source-template across your stack and pipelines.
If you installed it — respond
auth0-open-source-template 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 auth0-open-source-template 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 auth0-open-source-template 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. auth0-open-source-template on PyPI has been identified as a malicious package (version 20.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-004392024-12- sajansubediRLUA-2026-00120

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks auth0-open-source-template-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