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?

Remove @onum-releases/auth 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/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.

Can O3 Security detect @onum-releases/auth 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/auth and packages like it before any post-install script runs.

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

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

Scan your dependencies

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

Supply-chain protection