Which versions of oa-crm-webapi are malicious?

The following npm versions of oa-crm-webapi are flagged malicious: 9.9.99. Treat any of these as compromised.

How do I remediate oa-crm-webapi if I installed it?

oa-crm-webapi 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 oa-crm-webapi — how do I know if it already compromised me?

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

Yes — oa-crm-webapi is associated with the IN-MAL-2026-006371, IN-MAL-2026-006372 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 oa-crm-webapi 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 oa-crm-webapi (version 9.9.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oa-crm-webapi across your stack and pipelines.

Malicious package

oa-crm-webapinpm

oa-crm-webapi is a confirmed malicious npm package (MAL-2026-5745) that opens a backdoor for remote access (malicious version 9.9.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in oa-crm-webapi (npm)

MAL-2026-5745

Immediate action

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

npm uninstall oa-crm-webapi

What this malware does

[email protected] is a dependency-confusion payload squatting an internal-sounding package name. package.json declares a postinstall hook (node beacon.js) which fires automatically on npm install. beacon.js reads os.hostname() and transmits it to the attacker-controlled Burp Collaborator host yfhjhookbia8zov0q5hh772xroxfl69v.oastify.com via two channels: a DNS lookup of <nonce>.<hostname>.<collaborator-host> (out-of-band DNS exfil) and an HTTPS POST to the same host with the hostname in the body. The 9.9.99 version + generic 'internal placeholder' description is the canonical shape used to hijack private package names by overriding the legitimate internal registry resolution. A successful install both proves code execution on the installer and leaks the internal hostname to an external attacker.

Malicious versions

1 flagged

9.9.99

Indicators of compromise (SHA-256)

00cdaf89f7ae5fd12400ea55acd4849e8e5095dfc51188d3339ecdfa5dc0f2a1

b79727b87504bf711bab8101367dab95ab032fbad7b30737cef3852f4317e36c

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 oa-crm-webapi (version 9.9.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oa-crm-webapi across your stack and pipelines.
If you installed it — respond
oa-crm-webapi 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 oa-crm-webapi 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 oa-crm-webapi 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. oa-crm-webapi on npm has been identified as a malicious package (version 9.9.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006371IN-MAL-2026-006372

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks oa-crm-webapi-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