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

Be.Vlaaոԁeren.Basisregisters.BuildiոgRegistry.Api.BаckOfficeNuGet

Malicious code in Be.Vlaaոԁeren.Basisregisters.BuildiոgRegistry.Api.BаckOffice (NuGet) Remove it immediately and rotate any exposed credentials.

MAL-2024-4241
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
remove Be.Vlaaոԁeren.Basisregisters.BuildiոgRegistry.Api.BаckOffice

Malicious versions

1 flagged
3.85.2

Indicators of compromise (SHA-256)

d6df64490db641a599c2217bb3f4f516ad465e330899701fb5f1098dc884629c

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 Be.Vlaaոԁeren.Basisregisters.BuildiոgRegistry.Api.BаckOffice (version 3.85.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging Be.Vlaaոԁeren.Basisregisters.BuildiոgRegistry.Api.BаckOffice across your stack and pipelines.

  2. If you installed it — respond

    Remove Be.Vlaaոԁeren.Basisregisters.BuildiոgRegistry.Api.BаckOffice 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 Be.Vlaaոԁeren.Basisregisters.BuildiոgRegistry.Api.BаckOffice 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 Be.Vlaaոԁeren.Basisregisters.BuildiոgRegistry.Api.BаckOffice 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. Be.Vlaaոԁeren.Basisregisters.BuildiոgRegistry.Api.BаckOffice on NuGet has been identified as a malicious package (version 3.85.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-02909

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks Be.Vlaaոԁeren.Basisregisters.BuildiոgRegistry.Api.BаckOffice-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.

Be.Vlaaոԁeren.Basisregisters.BuildiոgRegistry.Api.BаckOffice (NuGet) malicious package — MAL-2024-4241 | O3 Security