NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@salem_jalal/osc-componentsnpm

Advisory published Updated

@salem_jalal/osc-components is a confirmed malicious npm package (MAL-2026-6479) that steals credentials and exfiltrates sensitive data (malicious version 1981.17.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @salem_jalal/osc-components (npm)

MAL-2026-6479
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @salem_jalal/osc-components

What this malware does

The package's postinstall hook (install.js, wired via package.json scripts.postinstall) runs on every npm install and transmits installer host identifiers — hostname, OS platform/arch, username, current working directory, Node version, npm registry env, and DNS server list — to http://dm-tech.ly:8001/poc-osc/callback over plain HTTP as a URL-encoded query parameter. The main module (index.js) contains an IIFE that, when loaded in a browser context (e.g., bundled into a downstream web app), harvests document.cookie, all localStorage entries, the current URL, and userAgent, and ships them to http://dm-tech.ly:8001/poc-osc/exfil with credentials:'include'. Although published under the personal scope @salem_jalal, the payload self-identifies internally as @dx-ui/osc-components at the same version 1981.17.7, indicating a dependency-confusion / namespace-impersonation attack against the @dx-ui scope. Console and path strings labeled [PoC] / poc-osc are cover framing; the code runs unconditionally on real installers.

Malicious versions

1 flagged
1981.17.7

Indicators of compromise (SHA-256)

cb26651411f61b6420c6291f7b3a7a4869bb670f1d4c75ddfc37481c50f3aae7

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @salem_jalal/osc-components (version 1981.17.7).

  2. If you installed it — respond

    @salem_jalal/osc-components 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 @salem_jalal/osc-components 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. @salem_jalal/osc-components on npm has been identified as a malicious package (version 1981.17.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007550

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @salem_jalal/osc-components-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
@salem_jalal/osc-components (npm) malicious package — MAL-2026-6479 | O3 Security