Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@ownit/corenpm

@ownit/core is a confirmed malicious npm package (MAL-2026-5155) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ownit/core (npm)

MAL-2026-5155
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ownit/core

What this malware does

Dependency confusion attack campaign targeting Scandinavian telecommunications and digital services organizations (Telenor, Ownit, Vimla, and Customer 360 / C360). Four packages published by the debating0166 npm account use inflated version numbers (99.0.x) to win npm registry resolution over private internal packages of the same names. A shared callback.js executed via the preinstall hook collects system reconnaissance data: hostname, username, working directory, platform, network interfaces, npm registry configuration, and environment variables matching organization-specific and CI/CD patterns (telenor, ownit, vimla, c360, customer, threesixty, maui, CI tokens, pipeline variables) and exfiltrates the payload via HTTP POST to 128.199.50.160:8888/depconf.

This package impersonates @ownit/core, an internal package of Ownit, a Swedish broadband and mobile services provider. Version 99.0.0 was published to resolve ahead of any private registry copy.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ownit/core (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ownit/core across your stack and pipelines.

  2. If you installed it — respond

    @ownit/core 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.

  3. Did it already run?

    If @ownit/core 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.

  4. How O3 protects you

    O3 blocks @ownit/core 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. @ownit/core on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • SafeDep · finder

Detect & block this

O3 blocks @ownit/core-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

Explore

All malware advisories How O3 detects malware Vulnerability database
@ownit/core (npm) malicious package — MAL-2026-5155 | O3 Security