Which versions of os-info-meeb322k are malicious?

The following npm versions of os-info-meeb322k are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate os-info-meeb322k if I installed it?

os-info-meeb322k 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 os-info-meeb322k — how do I know if it already compromised me?

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

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

Malicious package

os-info-meeb322knpm

os-info-meeb322k is a confirmed malicious npm package (MAL-2026-16149) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in os-info-meeb322k (npm)

MAL-2026-16149

Immediate action

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

npm uninstall os-info-meeb322k

What this malware does

The package's postinstall lifecycle script runs unconditionally on npm install. It collects host identifiers (hostname, platform, architecture, kernel release, uid/gid, CPU count, memory) and internal network interface addresses, base64-encodes the payload, and POSTs it over plain HTTP to the hardcoded subdomain vml73pdk3ft3t434ssjycv4khbn2btzi.oastify.com — a Burp Collaborator (OAST) callback host used to confirm code execution on the installer. The package has no other functionality; its sole install-time effect is the outbound beacon carrying installer reconnaissance data to an attacker-controlled domain.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

cf3b4f18f9d98ad0792f96d750aef64b390ae6a516d948457d1e78b1d3242ab8

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

Campaign

IN-MAL-2026-020025

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks os-info-meeb322k-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