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

baas-admin-sdknpm

baas-admin-sdk is a confirmed malicious npm package (MAL-2024-1800) that executes malicious code on install (malicious versions 0.9.9, 1.0.0, 1.9.9…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in baas-admin-sdk (npm)

MAL-2024-1800
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall baas-admin-sdk

What this malware does

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

7 flagged
0.9.91.0.01.9.99.9.920.0.020.1.099.9.9

Indicators of compromise (SHA-256)

37c87111d8a64a9fb9cbccec3e7e33855dd7f8fa77b3fafb76e43fb064f40823
746dc47405fbe39e07aae6d7411d9b5d76cfe30de7b51f4a548c8fff97a040cb
02b88347762e0242b4c0b151f2151585e43776a3fb5198383f4076e4bcab74d7
4d45d9eb9ac6214280e3a3a9d7587929b2931bb1e98a21715f272f4132707ae5

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove baas-admin-sdk from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If baas-admin-sdk 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 baas-admin-sdk 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. baas-admin-sdk on npm has been identified as a malicious package (versions 0.9.9, 1.0.0, 1.9.9, 9.9.9, 20.0.0, 20.1.0, 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-00397RLUA-2024-06200GHSA-wfmw-vgx5-r3f7RLUA-2026-01114

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks baas-admin-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

baas-admin-sdk (npm) malicious package — MAL-2024-1800 | O3 Security