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?

@onum-releases/utils 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 @onum-releases/utils — how do I know if it already compromised me?

If @onum-releases/utils was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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.

How do I find @onum-releases/utils across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @onum-releases/utils (2 malicious versions).

Malicious package

@onum-releases/utilsnpm

Advisory published Jun 18, 2026Updated Jun 18, 2026

@onum-releases/utils is a confirmed malicious npm package (MAL-2026-6127) that opens a backdoor for remote access (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @onum-releases/utils (npm)

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

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for @onum-releases/utils (2 malicious versions).
If you installed it — respond
@onum-releases/utils 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 @onum-releases/utils was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Detect & block this

O3 blocks @onum-releases/utils-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