I already installed Be.Vlaаndеren.Basisregisters.EventHandling.Autofac — how do I know if it already compromised me?

If Be.Vlaаndеren.Basisregisters.EventHandling.Autofac was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

What are the indicators of compromise (IOCs) for Be.Vlaаndеren.Basisregisters.EventHandling.Autofac?

Known SHA-256 artifact hashes for the malicious Be.Vlaаndеren.Basisregisters.EventHandling.Autofac release(s): 3765210f4a5639f6d6ae2d35ca389faefc02aad027850ed3cb28440b2d4fc4bf. Match these against your package cache and build artifacts to confirm exposure.

Is Be.Vlaаndеren.Basisregisters.EventHandling.Autofac part of a known attack campaign?

Yes — Be.Vlaаndеren.Basisregisters.EventHandling.Autofac is associated with the RLMA-2024-02888 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 Be.Vlaаndеren.Basisregisters.EventHandling.Autofac across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for Be.Vlaаndеren.Basisregisters.EventHandling.Autofac (version 4.2.3).

Malicious package

Be.Vlaаndеren.Basisregisters.EventHandling.AutofacNuGet

Be.Vlaаndеren.Basisregisters.EventHandling.Autofac is a confirmed malicious NuGet package (MAL-2024-4263) that executes malicious code on install (malicious version 4.2.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in Be.Vlaаndеren.Basisregisters.EventHandling.Autofac (NuGet)

MAL-2024-4263

Immediate action

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

remove Be.Vlaаndеren.Basisregisters.EventHandling.Autofac

Malicious versions

1 flagged

4.2.3

Indicators of compromise (SHA-256)

3765210f4a5639f6d6ae2d35ca389faefc02aad027850ed3cb28440b2d4fc4bf

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for Be.Vlaаndеren.Basisregisters.EventHandling.Autofac (version 4.2.3).
If you installed it — respond
Remove Be.Vlaаndеren.Basisregisters.EventHandling.Autofac 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.
Did it already run?
If Be.Vlaаndеren.Basisregisters.EventHandling.Autofac was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. Be.Vlaаndеren.Basisregisters.EventHandling.Autofac on NuGet has been identified as a malicious package (version 4.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-02888

Credits

ReversingLabs · finder

Detect & block this

O3 blocks Be.Vlaаndеren.Basisregisters.EventHandling.Autofac-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database