Which versions of @wbnr/frontend-shared are malicious?

The following npm versions of @wbnr/frontend-shared are flagged malicious: 99.0.0, 99.0.1. Treat any of these as compromised.

How do I remediate @wbnr/frontend-shared if I installed it?

Remove @wbnr/frontend-shared 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.

I already installed @wbnr/frontend-shared — how do I know if it already compromised me?

If @wbnr/frontend-shared 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.

Is @wbnr/frontend-shared part of a known attack campaign?

Yes — @wbnr/frontend-shared is associated with the IN-MAL-2026-016680, IN-MAL-2026-016675, RLMA-2026-10656 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 @wbnr/frontend-shared across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @wbnr/frontend-shared (2 malicious versions).

Malicious package

@wbnr/frontend-sharednpm

Advisory published Aug 6, 2026Updated Sep 24, 2026

@wbnr/frontend-shared is a confirmed malicious npm package (MAL-2026-13436) that executes malicious code on install (malicious versions 99.0.0, 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @wbnr/frontend-shared (npm)

MAL-2026-13436

Immediate action

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

npm uninstall @wbnr/frontend-shared

What this malware does

The package declares a preinstall lifecycle script (preinstall.js) that automatically runs on npm install. The script reads the installer's OS username (from process.env USER/USERNAME) and hostname (os.hostname()), embeds them into a subdomain of a hardcoded 4otph6fase1x2won0hrfzul2wt2qqge5.oastify.com callback host, and transmits them via both a DNS lookup and an HTTPS GET to that host at path /depconf/. The behavior is consistent with a dependency-confusion probe using Burp Collaborator (oastify.com) infrastructure; installer identifiers (username, internal hostname, timestamp, package name) are disclosed to a third-party callback domain on every install.

Malicious versions

2 flagged

99.0.099.0.1

Indicators of compromise (SHA-256)

6208a0da32b8b7ae795d85ecbf95788b876729db08b0a595ad24f05a02dbbdbe

d10e6da61faa186ed684c79707395158b1fd639ebe55ab4b36f13d8f98789fa1

4a79c3e3ce71d3606fd677207cd089ab148f2a7bae8fe546a2f3dfb13349eef3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @wbnr/frontend-shared (2 malicious versions).
If you installed it — respond
Remove @wbnr/frontend-shared 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 @wbnr/frontend-shared 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. @wbnr/frontend-shared on npm has been identified as a malicious package (versions 99.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016680IN-MAL-2026-016675RLMA-2026-10656

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @wbnr/frontend-shared-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