MAL-2026-18400: Malicious code in dowload_ebok_nur_mal_schnell_das_mammut_retten_by_knut_kruger_eva_schoffmann_davidov_ouz6t (npm)

Published Oct 29, 2026
·
Updated

--- -= Per source details. Do not edit below this line.=-

Source: amazon-inspector (097a05ce21d55f308b754a0dfea3bc1d16b0096187cb6201926527754781fd56) Package contains two files with no a static rule matches and no traced installer-harming behavior. No lifecycle scripts, no network activity, no credential or filesystem access, and no obfuscated or fetched code paths were observed. The package name resembles placeholder or test content rather than a functional library, and the version string (0.0.0-stage) is consistent with a staging or pre-release artifact.

Source: ghsa-malware (e3186ecbf422a5269d156a1c028f6b2507d2a6c4c81edb8b4bc0a3ba61bdb8f8) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Affected Software

1 affected component
npm/dowload_ebok_nur_mal_schnell_das_mammut_retten_by_knut_kruger_eva_schoffmann_davidov_ouz6t*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove dowload_ebok_nur_mal_schnell_das_mammut_retten_by_knut_kruger_eva_schoffmann_davidov_ouz6t from your environment.

    Remove the npm package from any computer where it is installed or running; removing it may not remove all malicious software resulting from its installation.

  2. Operational

    Rotate all secrets and keys stored on the affected computer immediately, using a different computer.

Event History

Oct 29, 2026
Advisory Published
via OSV·10:14 PM
Data Sourced
via OSV·10:14 PM
DescriptionAffected Software

Frequently Asked Questions

1

What systems should be treated as exposed?

Any computer where the package is installed or running should be considered fully compromised. This includes systems that may contain stored secrets or keys.

2

What should be done immediately after discovering this package?

Rotate all secrets and keys stored on the affected computer, using a different computer to perform the rotation. Remove the package from the affected system.

3

Is removing the package sufficient to remediate the system?

No. The available advisory warns that removal does not guarantee removal of all malicious software that may have resulted from installing it, because an outside entity may have obtained full control of the computer.

4

Was malicious runtime behavior observed in the inspected package contents?

One source reported no lifecycle scripts, network activity, credential or filesystem access, obfuscated code, fetched code paths, static-rule matches, or traced installer-harming behavior. However, another source advises treating installed or running systems as fully compromised.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203