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

internal-company-module-test-1337npm

Malicious code in internal-company-module-test-1337 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3249
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall internal-company-module-test-1337

What this malware does

The package internal-company-module-test-1337 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'internal-company-module-test-1337' @ 99.99.9994 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

4 flagged
99.99.999299.99.999499.99.999599.99.9996

Indicators of compromise (SHA-256)

07c2475e90b699654b9aa4a19c5ca0592001681d7a28996dc02ff7c31faf7343
e6c3688b939c7d34bd5baa1f6f6d982f8c42613281c8025a80b3fa5d42e55ee6
a239618b3ac37b6b893174de0e258eb36b3a0a104ed97bb29e78d41ee29d1055
daa07f251ccced0e7fc3db2fd9c5ad42a02551f7797b3a0f8745dd000c1783f3
ffa107cadda6301a772af8727ebafd976365c28371cddd211c176a57b12715d9

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for internal-company-module-test-1337 (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internal-company-module-test-1337 across your stack and pipelines.

  2. If you installed it — respond

    Remove internal-company-module-test-1337 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 activity or persistence.

  3. Did it already run?

    If internal-company-module-test-1337 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 internal-company-module-test-1337 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. internal-company-module-test-1337 on npm has been identified as a malicious package (versions 99.99.9992, 99.99.9994, 99.99.9995, 99.99.9996 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks internal-company-module-test-1337-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

internal-company-module-test-1337 (npm) malicious package — MAL-2026-3249 | O3 Security