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

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

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

@onum-releases/auth is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @onum-releases/auth — how do I know if it already compromised me?

If @onum-releases/auth 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 @onum-releases/auth part of a known attack campaign?

Yes — @onum-releases/auth is associated with the IN-MAL-2026-006989, IN-MAL-2026-006991, IN-MAL-2026-006990 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/auth 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 @onum-releases/auth (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @onum-releases/auth across your stack and pipelines.

Malicious package

@onum-releases/authnpm

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

MAL-2026-6123

Immediate action

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

npm uninstall @onum-releases/auth

What this malware does

On require('@onum-releases/auth'), index.js reads os.hostname() and issues an HTTP GET to auth.<hostname>.200majoeu01dk02xnjdajro1isojc90y.oastify.com, transmitting the installer's host identifier to a Burp Collaborator out-of-band domain via both DNS resolution and HTTP. The package.json self-identifies as a 'dependency-confusion / scope-takeover demonstration' placeholder under the @onum-releases scope, so any build that mistakenly resolves an internal @onum-releases/* name to the public registry will leak its hostname to a third-party collaborator endpoint. Although labeled a PoC, the import-time beacon performs unconsented exfiltration of installer-side data to an attacker-controlled domain.

Malicious versions

3 flagged

1.0.11.0.21.0.3

Indicators of compromise (SHA-256)

22d4bde1772d506f812e112fb8d6bfbf6a6f187dd823640f2cf15811f0d0633a

72203eaa09216d9c9eb3cb0202eba28ce4e44f14ee587608ddd8b0b62829dae6

75e6ff09332290e46dd6b6b660cdf20f335d18eddc93060373b5211ebab6f524

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @onum-releases/auth (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @onum-releases/auth across your stack and pipelines.
If you installed it — respond
@onum-releases/auth is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @onum-releases/auth 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 @onum-releases/auth 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. @onum-releases/auth on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006989IN-MAL-2026-006991IN-MAL-2026-006990

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @onum-releases/auth-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring