YCA A.I CyberSecurity Scoring
19/03/2026
Access Monitoring Plan
Access Monitoring Plan
No incidents recorded for Yara Clean Ammonia in 2026.
No incidents recorded for Yara Clean Ammonia in 2026.
No incidents recorded for Yara Clean Ammonia in 2026.
Anglo-Eastern's rich maritime heritage spans over 50 years of ship management, crew management, cruise & leisure management and technical services. We manage a diverse fleet of vessels worldwide on behalf of our global partners, and uniquely offer both cadet and crew training through our highly regarded maritime academy and strategically located training centres. From humble beginnings to industry pioneer, we are always looking to the future yet are never far from our roots, and it is this distinct blend of proactive forward-thinking and traditional values, coupled with our commitment to developing and nurturing our people and communities, that drives Anglo-Eastern and sets us apart from our peers. Leading with integrity and doing the right things the right way are at the heart of our work ethic and the foundation upon which we are able to build trust, drive performance and shape a better maritime future for generations to follow. Join us on our voyage in delivering excellence. ------------------------ IMPORTANT NOTICE | Anglo-Eastern does NOT use agents, and we do NOT charge fees in exchange for employment or AEMA sponsorship. We offer employment and sponsorship based on merit and suitability. Anyone asking for money in exchange for Anglo-Eastern employment or AEMA sponsorship is a fraudster. Please report such scammers and do NOT make any payments to them. COMMUNITY POLICY | We welcome our followers and other members of the LinkedIn community to comment on our posts and express their views. However, we have a zero-tolerance policy regarding comments that are obscene, threatening, discriminatory or of a harassing nature (including trolling), as well as those that intend to purposely mislead through false claims and misinformation, solicit, phish and/or otherwise scam. Such comments may be reported and/or removed at any time without notice.
About Hapag-Lloyd With a fleet of 313 modern container ships and a total transport capacity of 2.5 million TEU, Hapag-Lloyd is one of the world’s leading liner shipping companies. In the Liner Shipping segment, the Company has around 14,000 employees and 400 offices in 140 countries. Hapag-Lloyd has a container capacity of 3.7 million TEU – including one of the largest and most modern fleets of reefer containers. A total of 133 liner services worldwide ensure fast and reliable connections between more than 600 ports on all the continents. In the Terminal & Infrastructure segment, Hapag-Lloyd has equity stakes in 21 terminals in Europe, Latin America, the United States, India and North Africa. Around 3,000 employees are assigned to the Terminal & Infrastructure segment and provide complementary logistics services at selected locations in addition to the terminal activities.
Latest updates, reports, and threat intel affecting the global network.
Yara Clean Ammonia, an ammonia trader and shipper, has commenced the construction of the Yara Eyde flagship container vessel with a...
On September 5, 2025, Yara and partners began constructing Yara Eyde, the world's first renewable ammonia-fueled container ship.
Yara Clean Ammonia has chartered two medium gas carriers (MGCs) from Navigator Amon Shipping under long-term agreements.
A consortium successfully conducted ship-to-ship transfers of ammonia at anchorages within the Port of Dampier on 14 September 2024.
The Norwegian Directorate for Civil Protection gave their approval to the construction of the planned ammonia bunkering facility in Norway.
The Yara Eyde is set to become the world's first ammonia-powered container vessel. It will run on clean ammonia, serving routes between Norway and Germany.
Yara Eyde Bow Yara Eyde illustration of bow Yara Eyde Profile Illustration of Yara Eyde profile Yara Eyde Aft Yara Eyde Aft Yara Eyde Route...
Yara Clean Ammonia, NorthSea Container Line, and Yara International are joining forces to realize the world's first container ship that will use pure ammonia...
Chemical manufacturer, BASF, and Yara Clean Ammonia (YCA) have launched a joint study to develop and build a world-scale low-carbon blue...
In Zephyr's userspace dynamic-objects subsystem, thread_idx_alloc() in kernel/userspace/userspace.c allocated a new thread permission index from the global _thread_idx_map[] bitmap without holding lists_lock. On SMP systems, two user-mode threads invoking the k_object_alloc(K_OBJ_THREAD) syscall concurrently can both observe the same low free bit, perform the same non-atomic RMW to clear it, and return the identical tidx. The two newly created K_OBJ_THREAD objects are then assigned the same thread_id, so the two user threads alias a single bit position in every kernel object's perms[] bitfield: any subsequent grant of access on a kernel object to one thread is implicitly a grant to the other, defeating userspace ACL isolation. A secondary lost-update window between the unlocked &=~BIT() in alloc and the locked |= BIT() in thread_idx_free() can also leak entries from the thread-index pool. The defect is reachable from any user-mode thread via the unrestricted __syscall k_object_alloc and is gated on CONFIG_USERSPACE, CONFIG_DYNAMIC_OBJECTS, and CONFIG_SMP. The flaw was introduced when the per-thread permission index was added in 2018 and is present in every release up to and including v4.4.0. Fixed by holding lists_lock across the bitmap RMW and the permissions clear (and inlining the obj_list traversal that previously took the lock itself).
OpenRemote before 1.26.2 contains an authentication bypass vulnerability in the console registration API that allows unauthenticated attackers to update existing console assets by supplying a known asset identifier. Attackers can overwrite push notification tokens and console metadata without authentication or ownership validation, redirecting notifications or denying delivery to legitimate consoles.
SiYuan before v3.7.2 contains a missing authorization vulnerability in the POST /mcp kernel endpoint, which is gated only by a general auth check (model.CheckAuth) with no admin-role or read-only enforcement. This exposes 31 MCP tools, including a file tool with list/read/write/delete/rename/copy actions across the entire workspace. When the Publish server is enabled in anonymous mode (Conf.Publish.Enable=true and Conf.Publish.Auth.Enable=false), the Publish reverse proxy attaches an anonymous RoleReader JWT to proxied requests, allowing a remote unauthenticated attacker to reach /mcp. The attacker can read conf/conf.json to extract accessAuthCode, api.token, and cookieKey in plaintext, write arbitrary files in the workspace, and plant a plugin into data/plugins/ that executes with nodeIntegration:true and no contextIsolation on the next desktop launch, leading to administrator takeover.
ImageMagick before 7.1.2-27 contains a memory leak vulnerability in the magick command-line interface when invalid options are provided. Attackers can trigger memory exhaustion by repeatedly supplying malformed command-line arguments to consume system resources.
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - remove unused character device and IOCTLs The QAT driver exposes a character device (qat_adf_ctl) with IOCTLs for device configuration, start, stop, status query and enumeration. These IOCTLs are not part of any public uAPI header and have no known in-tree or out-of-tree users. Device lifecycle is already managed via sysfs. The ioctl interface also increases the attack surface and is the subject of a number of bug reports. Remove the character device, the IOCTL definitions, and the related data structures (adf_dev_status_info, adf_user_cfg_key_val, adf_user_cfg_section, adf_user_cfg_ctl_data). Drop the now-unused adf_cfg_user.h header and strip adf_ctl_drv.c down to the minimal module_init/module_exit hooks for workqueue, AER, and crypto/compression algorithm registration. Clean up leftover dead code that was only reachable from the removed IOCTL paths: adf_cfg_del_all(), adf_devmgr_verify_id(), adf_devmgr_get_num_dev(), adf_devmgr_get_dev_by_id(), adf_get_vf_real_id() and the unused ADF_CFG macros. Additionally, drop the entry associated to QAT IOCTLs in ioctl-number.rst.
curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?
linkedin_id=axa' -H 'apikey: YOUR_API_KEY_HERE'
Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.
Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.