Which versions of @onum-releases/utils are malicious?

The following npm versions of @onum-releases/utils are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate @onum-releases/utils if I installed it?

Remove @onum-releases/utils 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is @onum-releases/utils part of a known attack campaign?

Yes — @onum-releases/utils is associated with the IN-MAL-2026-007002, IN-MAL-2026-007001 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect @onum-releases/utils in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @onum-releases/utils and packages like it before any post-install script runs.

Malicious package

@onum-releases/utilsnpm

Malicious code in @onum-releases/utils (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6127

Immediate action

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

npm uninstall @onum-releases/utils

What this malware does

On require('@onum-releases/utils'), index.js reads os.hostname() and issues an HTTP GET to 'utils.<hostname>.200majoeu01dk02xnjdajro1isojc90y.oastify.com', leaking the installer's hostname via DNS and HTTP to an out-of-band collaborator endpoint controlled by the package publisher. The beacon fires unconditionally on module load, so any consumer that imports the package exposes its host identifier to the attacker-controlled collaborator. The package.json description claims 'Security PoC placeholder - benign, no runtime payload', directly contradicting the shipped code. The scope '@onum-releases' impersonates the Onum vendor namespace, consistent with a dependency-confusion lure aimed at that organization's developers.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

057e9534a55fd4068aaffb080224c08a14689dedbeb0737bda03a4c3bbc14a63

887866a4734ebf64a639f9d2512cd400085469ec7fa06aba5f1bbe340b2688b8

Frequently asked questions

No. @onum-releases/utils on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007002IN-MAL-2026-007001

References

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection