Which versions of ohcm-culture-formatting are malicious?

The following npm versions of ohcm-culture-formatting are flagged malicious: 5.0.0. Treat any of these as compromised.

How do I remediate ohcm-culture-formatting if I installed it?

ohcm-culture-formatting is a typosquat — you almost certainly intended a legitimately-named package. Remove ohcm-culture-formatting, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed ohcm-culture-formatting — how do I know if it already compromised me?

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

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

Malicious package

ohcm-culture-formattingnpm

Malicious code in ohcm-culture-formatting (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10128

Immediate action

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

npm uninstall ohcm-culture-formatting

What this malware does

[email protected] declares a preinstall hook ("preinstall": "node index.js") that auto-executes on npm install. index.js uses child_process.exec to run a shell pipeline that reads /etc/passwd, /etc/hosts, /etc/shadow, and id output, base64-encodes the concatenation, and POSTs it via curl to http://d98fu4tmls2g936th9qgfxje1qj9g91a6.oast.fun/ohcm-culture-formatting/$(whoami)/$(hostname)/, embedding the installer's username and hostname in the URL path and the file contents in the User-Agent header. The destination is an Interactsh/OAST out-of-band interaction collector. The package name mimics an internal ADP/Lifion (ohcm-*) namespace and the description string is Lifion host, consistent with a dependency-confusion payload targeting that internal namespace.

Malicious versions

1 flagged

5.0.0

Indicators of compromise (SHA-256)

5679f4434881406ce5af055e04a3ab7403158df3404c928a7fbc67596d0e9631

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ohcm-culture-formatting (version 5.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ohcm-culture-formatting across your stack and pipelines.
If you installed it — respond
ohcm-culture-formatting is a typosquat — you almost certainly intended a legitimately-named package. Remove ohcm-culture-formatting, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If ohcm-culture-formatting 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 ohcm-culture-formatting 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. ohcm-culture-formatting on npm has been identified as a malicious package (version 5.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009616

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ohcm-culture-formatting-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