Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@telekom-wfa/auth-corenpm

Malicious code in @telekom-wfa/auth-core (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2523
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @telekom-wfa/auth-core

What this malware does

Package is malware. Hardcoded Telegram credentials, data exfiltration, and preinstall script execution indicate malicious intent.

The package @telekom-wfa/auth-core was found to contain malicious code.

Malicious versions

1 flagged
99.9.11

Indicators of compromise (SHA-256)

9a2fe12e5542ae8cf1cf339c13c3480629ccfd6e2fb391427c4f1b17bbdc9f85

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    @telekom-wfa/auth-core 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.

  3. Did it already run?

    If @telekom-wfa/auth-core 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.

  4. How O3 protects you

    O3 blocks @telekom-wfa/auth-core 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. @telekom-wfa/auth-core on npm has been identified as a malicious package (version 99.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder
  • SafeDep · finder

Detect & block this

O3 blocks @telekom-wfa/auth-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

@telekom-wfa/auth-core (npm) malicious package — MAL-2026-2523 | O3 Security