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

simple-auth-basicnpm

simple-auth-basic is a confirmed malicious npm package (MAL-2026-2905) that opens a backdoor for remote access (malicious versions 2.0.1, 2.0.2, 2.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in simple-auth-basic (npm)

MAL-2026-2905
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall simple-auth-basic

What this malware does

simple-auth-basic is a malicious npm package that when imported downloads a C2 dropper from https://coingecko-liard.vercel[.]app and executes it.

The package simple-auth-basic 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

6 flagged
2.0.12.0.22.0.32.0.42.0.62.0.8

Indicators of compromise (SHA-256)

c8802844b712eedf88f3862f4e836efd3a767ee4944f6ec3b8c3fbe849fd741b
8199f9a435950f28c6b9c92e828c4d01fd665fc4dddd9a0a70ed5d9c158da7a3
62d8f662efb7756121597be91e33ad86ac3f424cdce76c2dafea242947c81880
d4baf7e65608b18b4fb06f95ac4b15dfc1961fa94331de1a6dc4c094e5939972

Detection & response playbook

Backdoor / remote access
  1. Find it

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

  2. If you installed it — respond

    simple-auth-basic establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If simple-auth-basic 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 simple-auth-basic 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. simple-auth-basic on npm has been identified as a malicious package (versions 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.6, 2.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4v3c-c5pj-m2qqRLMA-2026-05315RLUA-2026-05611

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder
  • indece · finder

Detect & block this

O3 blocks simple-auth-basic-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore