Which versions of 8jfiesaf83 are malicious?

The following npm versions of 8jfiesaf83 are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.0.10, 1.0.11. Treat any of these as compromised.

How do I remediate 8jfiesaf83 if I installed it?

Remove 8jfiesaf83 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 8jfiesaf83 — how do I know if it already compromised me?

If 8jfiesaf83 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 8jfiesaf83 part of a known attack campaign?

Yes — 8jfiesaf83 is associated with the RLMA-2025-05672, RLUA-2025-06052, RLUA-2026-05955 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 8jfiesaf83 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 8jfiesaf83 (12 malicious versions).

Malicious package

8jfiesaf83npm

Advisory published Nov 3, 2025Updated Sep 1, 2026

8jfiesaf83 is a confirmed malicious npm package (MAL-2025-49331) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 8jfiesaf83 (npm)

MAL-2025-49331

Immediate action

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

npm uninstall 8jfiesaf83

What this malware does

The package 8jfiesaf83 was found to contain malicious code.

Malicious versions

12 flagged

1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.91.0.101.0.11

Indicators of compromise (SHA-256)

5ef67af98dc92779c9c7da804d6673f1838980f53e7376335dae65a375877a2e

3ff14cbd915dc978cafe2cd12dfbcac3496587b46605a567ca668fe11c89831d

27c7d8e5e1f8a9d16737601f11fb2de5ef394687b827d2b9e85210dbb2f735ee

08ce3b6d02167ff31742795708232f147fcc91506fee7c9ad46640adb27fdd6d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for 8jfiesaf83 (12 malicious versions).
If you installed it — respond
Remove 8jfiesaf83 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 8jfiesaf83 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. 8jfiesaf83 on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, and 4 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05672RLUA-2025-06052RLUA-2026-05955

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks 8jfiesaf83-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