Which versions of fixerpabo_jkbts are malicious?

The following npm versions of fixerpabo_jkbts are flagged malicious: 1.0.0, 1.1.0. Treat any of these as compromised.

How do I remediate fixerpabo_jkbts if I installed it?

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

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

Yes — fixerpabo_jkbts is associated with the RLMA-2026-01322 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 fixerpabo_jkbts across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fixerpabo_jkbts (2 malicious versions).

Malicious package

fixerpabo_jkbtsnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

fixerpabo_jkbts is a confirmed malicious npm package (MAL-2026-1740) that executes malicious code on install (malicious versions 1.0.0, 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fixerpabo_jkbts (npm)

MAL-2026-1740

Immediate action

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

npm uninstall fixerpabo_jkbts

What this malware does

The package fixerpabo_jkbts was found to contain malicious code.

Malicious versions

2 flagged

1.0.01.1.0

Indicators of compromise (SHA-256)

863b717a5e6d393d2033e282ebf314e8858493f63be74f61b23abe25f151d3b1

148857b09579ef944127beae0fce66e973deb506e02c508853472b271d40bc0d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01322

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks fixerpabo_jkbts-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