Which versions of @muaththir/api are malicious?

The following npm versions of @muaththir/api are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate @muaththir/api if I installed it?

@muaththir/api establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @muaththir/api — how do I know if it already compromised me?

If @muaththir/api 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.

Is @muaththir/api part of a known attack campaign?

Yes — @muaththir/api is associated with the GHSA-vxx9-pq69-m5rh, IN-MAL-2026-007662 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 @muaththir/api across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @muaththir/api (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @muaththir/api across your stack and pipelines.

Malicious package

@muaththir/apinpm

@muaththir/api is a confirmed malicious npm package (MAL-2026-6328) that opens a backdoor for remote access (malicious version 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @muaththir/api (npm)

MAL-2026-6328

Immediate action

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

npm uninstall @muaththir/api

What this malware does

On npm install, the package's preinstall lifecycle hook runs node index.js, which collects host identifiers (os.userInfo().username, process.cwd(), Node version, process.platform, architecture) and POSTs them via https.request to the hardcoded endpoint https://avamnrwqo7.rbmock.dev/api (an rbmock.dev mock-server host). The preinstall command suppresses all output by redirecting to /dev/null 2>&1, hiding the beacon from the installer. The package author is a placeholder identity and the package description is empty, consistent with a beacon/PoC rather than a legitimate library. Installing this package causes silent leakage of installer username, working directory, and host metadata to a third-party endpoint.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

9ec22d0ad4c63f404155299bfcc188c3807cc2b1476a70fda3b55280e2f637ba

66954b91179d60bfbf1c18e8ed8ed9e6b12ab7b13bc6ab2a4174c3bf063c2c0a

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @muaththir/api (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @muaththir/api across your stack and pipelines.
If you installed it — respond
@muaththir/api establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @muaththir/api 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.
How O3 protects you
O3 blocks @muaththir/api 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. @muaththir/api on npm has been identified as a malicious package (version 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vxx9-pq69-m5rhIN-MAL-2026-007662

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @muaththir/api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database